From Containers to Kubernetes: A GitOps-Driven Platform on VMware VKS

How TeraSky helped a global financial services firm move from a single Docker host to a GitOps-driven Kubernetes platform on VMware VKS.

TeraSky helped a global financial services firm move from a single Docker host to Kubernetes, building a GitOps-driven platform on VMware VKS, using VMware Cloud Foundation infrastructure the firm already owned. TeraSky deployed the Kubernetes foundation, implemented Argo CD for Git-based delivery, added self-managed Tanzu Mission Control for multi-cluster management, and worked side by side with the firm’s engineers – who went on to deploy new clusters on their own.

Key Takeaways

• Built on existing infrastructure: The platform runs on the firm’s existing VMware Cloud Foundation footprint, using previously untapped VKS entitlements.
• From Docker host to orchestration: The firm moved from a single Docker host to a supervisor cluster and a dedicated application cluster.
• GitOps delivery: Argo CD introduced a declarative, Git-based deployment workflow.
• Multi-cluster management: A self-managed instance of Tanzu Mission Control provides centralized visibility and lifecycle management.
• Operational independence: After the project, the firm’s team deployed additional clusters in new environments without external oversight.
• Stack: VMware Cloud Foundation, VMware vSphere Kubernetes Service, Argo CD, GitOps, Tanzu Mission Control.

Running containers is not the same as running a container platform.

One global financial services firm was at exactly that point. It was actively running containerized applications, but the whole operation relied on a single Docker host. There was no orchestration layer, no formal Kubernetes infrastructure, and no repeatable way to scale applications.

The foundation was already in place, though. The firm’s existing investment in VMware Cloud Foundation (VCF) included untapped entitlements for VMware vSphere Kubernetes Service (VKS, formerly Tanzu Kubernetes Grid Service). That gave it a clear, built-in path to enterprise Kubernetes – it just needed to chart the course.

The Challenge: Moving From a Single Docker Host to Kubernetes

The initial goal was straightforward: configure the VMware Kubernetes layer on the firm’s existing VCF infrastructure.

But moving from a lone Docker host to a fully orchestrated environment is a major operational shift. It changes how applications are deployed, updated, and scaled every day. Spinning up clusters was not enough – the firm needed a complete platform ecosystem:

• Orchestration: automated orchestration in place of a single host.
• Delivery: Git-based application delivery.
• Lifecycle: visibility into the platform’s lifecycle.
• People: most importantly, an internal team ready to run it all.

Key Technical Decisions

How TeraSky Built the Platform

Deploying the Kubernetes Foundation on VCF

TeraSky began by deploying the core VMware Kubernetes infrastructure on the firm’s VCF footprint, setting up the supervisor cluster alongside a dedicated application cluster.

Introducing GitOps With Argo CD

With the foundation in place, the project evolved into platform engineering. To establish a modern, declarative deployment workflow, TeraSky implemented Argo CD and introduced the firm’s team to GitOps principles from the ground up.

Making Knowledge Transfer the Core of the Engagement

A platform is only as good as the team operating it. Instead of handing over a finished environment, TeraSky worked side by side with the firm’s engineers, building architectural knowledge, troubleshooting skills, and operational workflows into the team’s daily routines.

Adding Multi-Cluster Management With Tanzu Mission Control

Later, to support future growth, TeraSky deployed a self-managed Tanzu Mission Control instance, providing the firm with a single, centralized view for multi-cluster visibility and lifecycle management.

The Impact: Complete Platform Ownership

The firm has moved from basic container hosting to running a sophisticated, GitOps-driven Kubernetes platform on its existing infrastructure.

• A visible, repeatable delivery model: Pairing the VMware foundation with Argo CD and Tanzu Mission Control gave the firm a highly visible, easily repeatable way to deliver applications.
• Full operational independence: After the project formally ended, the firm’s team expanded the footprint on its own, deploying additional clusters in new environments without external oversight.
• A platform engineering organization: The firm shifted from a reactive container hosting model to a proactive, mature platform engineering organization.

“The truest measure of the project’s success was our immediate operational independence. After the project formally ended, our team successfully expanded the footprint, deploying subsequent clusters in new environments without external oversight. It was precisely what we had aimed for, and TeraSky made it happen.”
– Client Representative

Technologies Used

VMware Cloud Foundation | VMware vSphere Kubernetes Service (formerly Tanzu Kubernetes Grid Service) | Argo CD | GitOps workflows | Tanzu Mission Control

Frequently Asked Questions

How can an organization move from a single Docker host to Kubernetes?
Moving from a single Docker host to Kubernetes is a platform change, not just a cluster install: it changes how applications are deployed, updated, and scaled day to day. It calls for orchestration, Git-based application delivery, lifecycle visibility, and an internal team ready to operate the platform. For a global financial services firm, TeraSky deployed a supervisor cluster and a dedicated application cluster on VMware VKS, added Argo CD for GitOps and Tanzu Mission Control for multi-cluster management, and trained the firm’s engineers side by side.

What is the difference between running containers and running a container platform?
Running containers on a single Docker host provides no orchestration layer, no formal Kubernetes infrastructure, and no repeatable way to scale applications. A container platform adds automated orchestration, Git-based delivery, lifecycle visibility, and repeatable operating processes. A global financial services firm made this move with TeraSky, building a GitOps-driven Kubernetes platform on its existing VMware infrastructure.

Is Kubernetes included with VMware Cloud Foundation?
It can be, depending on the VCF agreement. One global financial services firm’s existing VMware Cloud Foundation investment included VMware vSphere Kubernetes Service (VKS) entitlements it had not used, which allowed TeraSky to build its Kubernetes platform on infrastructure the firm already owned.

Does Argo CD work with VMware vSphere Kubernetes Service?
Yes. Argo CD can provide a declarative, Git-based deployment workflow for applications on VKS clusters. TeraSky implemented Argo CD on a VKS-based platform for a global financial services firm and introduced its team to GitOps principles from the ground up.

What is Tanzu Mission Control used for?
Tanzu Mission Control provides centralized multi-cluster visibility and lifecycle management for Kubernetes. TeraSky deployed a self-managed instance for a global financial services firm so its clusters could be managed from a single view as the platform grew.

How do teams build the skills to run Kubernetes independently after an implementation?
By building knowledge transfer into the implementation itself rather than leaving it to a final handover. At a global financial services firm, TeraSky worked side by side with the engineers throughout, building architectural knowledge, troubleshooting skills, and operational workflows into their daily routines. After the project ended, the firm’s team deployed additional clusters in new environments without external oversight.

Building Your Kubernetes Platform?
TeraSky helps enterprise teams upgrade, extend, and operate Kubernetes platforms across on-premises and cloud environments, including complex workload, identity, and security requirements.

Explore TeraSky’s Application Infrastructure expertise or talk to our Kubernetes team.