Thumbnail image

Kubernetes With Continuous Delivery Included

Table of Contents


One of the features I have been looking most forward to, in Tanzu Mission Control (TMC) is the ability to deploy a new Kubernetes (K8S) cluster and enable Continuous Delivery, as part of the deployment.

What that means, is that the cluster, will fetch a config, from a Git repository, after deployment, and allow configurations to be handled, thru that.

So basically anything you can add as a Yaml file or Helm chart can be automatically applied.

Sounds complicated? Not at all. Here I will explain how to set it up, for all future deployments, with different configurations, depending on what group you select.


Before we begin, we need to create a Git repository. I have created one in Github, with the following structure

├── apps
│   ├── kustomization.yaml
│   └── nginx
│       ├── deployment.yaml
│       ├── kustomization.yaml
│       ├── namespace.yaml
│       └── service.yaml
├── base
│   ├── cert-manager
│   │   ├── api-token.yaml
│   │   ├── cert-manager.yaml
│   │   ├── clusterissuer.yaml
│   │   └── kustomization.yaml
│   ├── config
│   │   ├── clusterrole.yaml
│   │   └── kustomization.yaml
│   ├── contour
│   │   ├── contour.yaml
│   │   └── kustomization.yaml
│   └── kustomization.yaml
├── overlays
│   ├── production
│   │   ├── kustomization.yaml
│   │   └── namespace.yaml
│   └── test
│       ├── kustomization.yaml
│       └── namespace.yaml

It uses Kustomize for the structure, so if you are not familiar with that, then I recommend taking a look at their website. They has some good getting-started guides.

If you just want to get started fast, then I have included link to a basic sample repository, in the end of this blog post.

The concept is that I can point to overlays/production folder, for production workloads, and overlays/test for test workloads. All my base templates are in Apps and Base, and Kustomize can customize them, so they match the configuration I want in Production and Test.

We also need to be able to connect to the Github repo. This is done, by creating SSH keys.

I use the following command to generate my private and public keys.

ssh-keygen -t ecdsa -b 521 -C "[email protected]"

Then I add the public key, to my GitHub profile, and save my private key for later.

I also ran


And saved the output, to use in the next step.


In TMC, I have created 2 cluster groups, which I will be using for this.

production-cd and test-cd cd-groups

I enabled “continuous delivery” on the production group. enable-cd

Created Repository credentials with a name, my private key, and the output from the ssh-keyscan command. git_credentials

In Git repositories, I added my repository and pointed it to the credentials I created in the last step. Note the SSH URL for my repo is in the following format ssh:// The branch also needs to be set to main, under advanced settings (or whatever your branch is) git_repo

Last I added a Kustomization, with a name, my repository, and the path overlays/production for my production cluster group.

I also enable “Prune” under advanced settings. kustomization

And then I did the same, for the test-cd cluster group. The only change is that the path is overlays/test instead.


All there’s left now is to deploy a new cluster using TMC, or to attach an existing one, and add it to the cluster group.

I have created one, and attached it to the test-cd group. attach_cluster

Right after attaching it to TMC, I can see it says reconciling which means it’s enabling continuous delivery and applying the configurations. reconciling

A simple k get ns shows that a test namespace has been created.

This is specific for the overlays/testfolder

But I can also see projectcontour, cert-manager, nginx there. namespace Running k get secrets -n cert-manager shows that my Cloudflare secret, has been applied, so I can pull new certificates, using the Clusterissuer, that is also installed. secret

This means all my configurations, have been applied, without me having to do anything, and my colleagues that use the same platform, can deploy K8S clusters, pre-configured, with the settings they need.

Also if I change or add anything, it will be applied, within the next 5 minutes.

Pretty neat, or what do you think?

Sample Repository

For quick getting started, I have created a basic Sample repository, that you can fork and use to get started fast.

Photo by carlos aranda on Unsplash

Related Posts