A Kubernetes service catalog built with Helm, GitOps, and vCluster can give developers a self-service route to deploy services while platform teams retain control over how infrastructure is composed and changes reach environments. The key is to keep CI’s role distinct from GitOps reconciliation: CI validates or generates deployable artifacts, while a GitOps controller synchronizes approved desired state from Git to Kubernetes.
What the Kubernetes catalog workflow is meant to solve
The phrase “from CI to Kubernetes catalog” describes a platform workflow, not a single product or turnkey recipe. A developer should be able to request or configure a service through a catalog; platform components then package the service, compose any required infrastructure, and deliver the declared configuration to an appropriate cluster.
As an Amazon Associate I earn from qualifying purchases.
The May 13, 2025 vCluster webinar framed this around Helm-based service deployment, infrastructure composition with Terraform, Kratix, and Score, label-based Argo CD deployment across multiple vClusters, and CI-generated GitOps-ready manifests. Those agenda items show the intended scope, but the event page does not prescribe a complete implementation or establish that one design fits every organization. See the webinar agenda.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesHow CI and GitOps divide the work
A typical GitOps architecture includes a Git repository for desired state, a CI/CD pipeline to build, test, or package code, a Kubernetes cluster running workloads, and a GitOps operator that watches the repository and synchronizes cluster state. In a review-based workflow, a change is pushed to Git, reviewed, approved, and merged; the controller then reconciles the target environment against the merged configuration. vCluster’s GitOps overview describes these components and this workflow.
#1 Best Overall
| Stage | What happens | Primary responsibility |
|---|---|---|
| Change and review | A developer updates service or infrastructure configuration and submits it through the repository’s review process. | Git records the desired state and the approval process controls which changes are merged. |
| Validation and generation | CI can test changes, build or package code, and generate manifests or other deployable artifacts. | CI prepares and checks inputs; it need not be the component continuously applying cluster state. |
| Reconciliation | A GitOps controller observes the repository and aligns the target environment with the declared state. | The controller applies the approved desired state and continues to reconcile drift. |
This boundary is useful because it clarifies where to investigate failures: a failed build or manifest-generation job belongs to CI, while a controller that cannot apply a merged change is a reconciliation or target-environment issue. Implementations vary, so the table describes the roles in the cited architecture rather than mandatory behavior for every toolchain.
Where vCluster fits
A virtual cluster runs within a namespace on a host Kubernetes cluster but appears to its users like a standalone Kubernetes cluster. That makes vCluster a possible target for a catalog that needs separate Kubernetes control planes without treating every team environment as a wholly separate physical cluster. The distinction matters: the virtual cluster is hosted by an underlying cluster, so platform operators still have to account for the host and its operational boundaries. The definition and the historical Helm-based installation example appear in vCluster’s 2023 tutorial.
In a multi-vCluster design, the platform needs a deliberate way to map a service or team’s desired state to the intended target. The webinar agenda specifically raises label-based deployment with Argo CD, but the event page does not document exact labels, selection rules, or a working configuration. Treat labels as a targeting design to define and validate in your own Argo CD setup, not as a ready-made convention supplied by the agenda.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →How a self-service catalog can be assembled
Offer services through Helm
Helm charts can package Kubernetes applications for repeatable deployment, making them a natural unit for catalog entries. A catalog can expose supported services and the configuration a developer is permitted to change, while keeping platform-owned defaults and policies under review. The webinar identifies Helm-based service cataloging as a topic; it does not specify a catalog interface, chart schema, or governance model.
Rank #3
Compose infrastructure alongside applications
Some services need infrastructure as well as Kubernetes objects. The webinar names Terraform, Kratix, and Score as examples in the infrastructure-composition discussion. Their inclusion establishes that composition is part of the intended design space, not that these tools are interchangeable or that the session ranks them. Choose based on the interfaces your platform needs to expose, the systems it must integrate, and how teams will own and review the resulting desired state.
Generate GitOps-ready manifests
The agenda also describes Go-based templates and CI pipelines generating deploy-ready manifests for GitOps. In that pattern, CI turns a developer’s approved inputs into configuration suitable for a repository or deployment process; the GitOps controller remains responsible for reconciling the declared state to the selected target. The event source does not provide template examples or implementation details, so the specific generation flow must be designed for the platform’s own repository and controller.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Version and upgrade details can change the setup
Do not copy a dated vCluster command or configuration and assume it still matches the installed version. The 2023 Helm tutorial is useful for understanding the general concept, but its CLI commands, chart repository, distribution list, and examples are historical.
Free tools Windows power users keep installed
One-click scans. No signup required.
For a concrete version-specific change, vCluster’s August 15, 2024 v0.20 announcement says that release introduced a consolidated vcluster.yaml configuration and a unified Helm chart, changed the default control-plane distribution from k3s to Kubernetes, and did not support switching distributions as an upgrade path. These statements apply to v0.20, not automatically to later releases. Check the documentation for the version you intend to install before adopting configuration or planning upgrades. Read the v0.20 release announcement.
A practical design checklist
- Define the catalog contract: decide which services developers can request, which values they can set, and which defaults remain platform-managed.
- Separate validation from deployment: specify what CI tests or generates and what the GitOps controller applies and reconciles.
- Make approval explicit: use the repository workflow to establish which changes are allowed to reach the desired-state branch or location.
- Specify target selection: define how services map to clusters or vClusters, including any label-based Argo CD selection rules.
- Identify composition boundaries: determine which service requirements are Kubernetes resources and which require infrastructure composition.
- Pin the operational context: verify the vCluster version, configuration format, distribution choice, and upgrade path against current official documentation.
What the webinar does—and does not—establish
The webinar’s title and agenda are a useful map of the problem: connect CI, a self-service service catalog, infrastructure composition, Helm, GitOps, Argo CD, and vCluster. They do not supply a current deployment tutorial, comparative evaluation of Terraform, Kratix, and Score, or tested multi-vCluster configuration. Use the agenda to shape architecture questions, and rely on version-matched product documentation for executable steps.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
