Case Study
9 November, 2026
November 12, 2026
How TeraSky expanded Infrastructure-as-Code capabilities for TMC while building reusable tooling to streamline provider development.
Some technical consulting projects focus on implementing software. Others sit directly inside the product itself.
When VMware (now Broadcom’s VMware Division) needed to expand the integration between Tanzu Mission Control (TMC) and Terraform — the standard tool for managing IT infrastructure as code — they brought in TeraSky to serve as an extension of their internal product engineering organization.
Working side by side with VMware’s core developers, TeraSky expanded the official TMC Terraform Provider, giving enterprise customers automated control over more of their Kubernetes environments. While the new features provided immediate value to customers, the work also solved a broader engineering challenge: TeraSky built an automated schema converter that replaced manual code translation, streamlining VMware’s provider updates moving forward.
Tanzu Mission Control provides a central hub for managing Kubernetes clusters across public clouds and private data centers. As customer adoption grew, engineering teams wanted to manage more of TMC through code—including security policies, user permissions, cluster lifecycles, and data backups.
Expanding these capabilities wasn’t just a matter of writing new features. Every new Terraform option had to match VMware’s underlying system rules (APIs) precisely. Doing this translation manually across multiple coding layers was slow and repetitive, and it introduced the risk of small human errors that could break automated workflows.
Acting as an embedded extension of VMware’s product engineering team, TeraSky extended the TMC Terraform Provider to support key operational tasks:
These updates allowed platform engineering teams to manage complex Kubernetes operations entirely through code, eliminating manual configuration steps.
While building the new features, TeraSky identified a recurring inefficiency: developers spent significant time hand-coding the translation layer between VMware’s API models and Terraform schemas.
To solve this, TeraSky built an internal accelerator called the Terraform Schema Converter.
Instead of requiring engineers to manually map data structures line by line, the tool automates the conversion process. This removed tedious manual work, reduced coding errors, and provided VMware with a reusable asset that accelerates future Terraform provider updates.
| Challenge | What TeraSky Delivered | Long-Term Benefit |
| Limited automation options | Expanded coverage for policies, access roles, and cluster setup | Customers can manage TMC end-to-end using Terraform code |
| API translation errors | Mapped Terraform code directly to VMware’s OpenAPI standards | Prevents bugs and ensures code stays aligned with system APIs |
| Slow development cycles | Engineered the Terraform Schema Converter | Automates repetitive code translation, saving engineering hours |
VMware Tanzu Mission Control | Terraform | Infrastructure as Code | GoLang | OpenAPI / Swagger | Kubernetes | Terraform Provider SDK | VMware Tanzu ecosystem
The project gave VMware customers a much broader set of Infrastructure-as-Code capabilities for managing Kubernetes at scale. At the same time, the new converter tool simplified internal development, ensuring future features can be released faster and with greater consistency.
By delivering product-level code and developing reusable IP, TeraSky provided value well beyond traditional services, functioning as a true product engineering partner to strengthen VMware’s automation ecosystem for the long term.
8 November, 2026