I also wanted to call out that cndi is a great fit for deploying services that go beyond data management.
If you have the opportunity to deploy a new service, and you are trying to decide if you should buy a PaaS or self-host the system, the CNDI toolchain allows you to self-host with the ease of PaaS.
This is especially useful if you generally don’t work on infrastructure already and want a way to jump in quickly.
If you’re on a data team and you're looking to do orchestration with Airflow, or if you’re building a new web service and need a PostgreSQL database, CNDI is a great fit.
You can find a growing list of services cndi supports at https://cndi.dev/templates, but don’t forget you can also make your own!
- I want to deploy my own things with argo alongside this cluster, how?
- I want a private nlb, even locked by a vpn subnet, how?
- I want to put this in an existing vpc, or peer with a vpc, or tgw with a vpc, how?
- I want to specify some RI’s for my nodes, how? I want to use spot, how?
- How do I upgrade each separate piece of the stack?
I could keep going but I hope the point is clear, I think this is too much of an oversimplification of a complex system. Better to just use MWAA or pay a devops team.
> - I want to deploy my own things with argo alongside this cluster, how? So using "cndi init" command, cndi gives a repo that contains Iaac, Cluster Manifests and Application Manifests. Everything gets deployed on choice of your cloud once you push to github. Use helm charts or K8s yaml.
> - I want a private nlb, even locked by a vpn subnet, how? Not fully baked but there is a way to add NLB manifests.
> - I want to put this in an existing vpc, or peer with a vpc, or tgw with a vpc, how? Working on this.
> - How do I upgrade each separate piece of the stack? This needs to be looked into more.