cdk8s VS terraform-cdk

One apparent limitation of the CDK is that, at least for the nonce, it can only be used with AWS (there are two notable projects in the work right now that will greatly expand CDK's reach: cdk8s and cdktf). With Terraform you can use choose from a plethora of providers. Hell, I was able to set up my home network running on Unifi Dream Machine using Terraform. How cool is that?!

This is funny. We've been learning cdk8s at work and it keeps bringing the BTK killer to mind.

Either https://github.com/awslabs/cdk8s or something like https://dhall-lang.org/

How about https://github.com/awslabs/cdk8s

I would be remiss to not point out that both the Kubernetes CDK, awslabs/cdk8s, and Terraform CDK, hashicorp/terraform-cdk both already use projen.

At first I tested it to deploy an OVHcloud Managed Kubernetes Service (MKS) with a Node Pool. And step by step, it worked. I even created a Pull Request (PR) in the terraform-cdk repository to add it as an example ☺️.

I'll be trying more sample app deployments with CDK and maybe even explore CDK for Terraform.

You can use CDK with other providers using https://github.com/hashicorp/terraform-cdk

In my experience, CDK is far better than Pulumi, especially if you're mostly going to be using AWS.

I, personally, prefer Crossplane Composite Functions on top of CDK8S, but had dropped CDKTF due to bloat. You can actually manage Kubernetes updates/upgrade lifecycle with Crossplane, as well.

I was going to recommend Pulumi, but looks like CDK for Terraform is still being kept up to date.

Avoid Pulumi, get directly to source and use https://github.com/hashicorp/terraform-cdk