Use tags to switch between cdk8s L1 or cdk8s L2 examples.

cdk8s L2 example - TypeScript

In this example, I used cdk8s-plus-29 Layer 2 abstractions i.e. Deployment, Secret, etc. to define the kubernetes resources.

I used a deployment with 2 replica pods here to serve the issue app. Since the image is pulled from a private docker repo, I used a k8s secret of type dockerconfig to authenticate.

I couldn't find any way to add imagePullSecrets to a ServiceAccount using cdk8s-plus. So no ServiceAccount in this implementation. That's the only difference between the L2 & L1 examples. I added that property to the Pod props, see line 23.

dockerRegistryAuth: dockerSecret,

---

issue-app-github

• Check main.ts for cdk8s code

• Check issue-demo-example.k8s.yaml for the generated manifest

• Check dist folder for YAMLs.

---

screenshots

---

ArgoCD & cdk8s

For the most part, I'll assume people use GitOps with private repos.

For a public repo, I could've used ApiObject from cdk8s to make bitnami's Sealed Secrets for a Service Account and the Docker Registry Auth. But then I'd also have to copy paste the encrypted data, manually or through some scripting.

new ApiObject(this, 'git-sealed', {
      apiVersion: 'bitnami/v1alpha1',
      kind: "SealedSecret",
      metadata: {
        name: 'github-secret',
        namespace: 'argocd'
      },
      spec: {
        encryptedData:
        {
          sshPrivateKey: "someencryptedstring"
        }
      }

For this demo, I feel like creating k8s objects by translating it into TypeScript would defeat the purpose of cdk8s-plus.