Agree?... so I think it's time to build my own internal platform.
So... after deploying numerous applications to my home Kubernetes cluster, I've realized one thing. I want to be able to get a production-ready application running as quickly as possible. My usual approach is to copy my Kubernetes template folder and modify…
So... after deploying numerous applications to my home Kubernetes cluster, I've realized one thing. I want to be able to get a production-ready application running as quickly as possible. My usual approach is to copy my Kubernetes template folder and modify the YAML files for every new project. It works. But now I'm repeating the same process every time I start a new application. I think it's time to solve that problem. Instead of copying templates and editing YAML, I want to build my own internal platform tool. Anyone has build kinda similar solution? What are some key components to consider? If you're also deploying applications on Kubernetes and need a starter template, you can check out mine on GitHub.
已收录讨论
Look into kustomize
I already use Kuztomize… but I am looking at a a scalable way where I can deploy database, backend, client k8s applications
This is the way
Helm or kustomize. And, Database=backend
Yes, for over a decade and hundreds of charts across multiple companies. It’s rare to come across someone not using helm, it’s how pretty much every OSS k8s app is packaged. Sometimes people use kustomize instead (or with helm). What about helm don’t you like? If set up properly it’s about as DRY as can be.
Build helm charts of your applications! They can be deploy as many times as you like, you can save them to your docker registry, and customization is just a different values file.
That sounds cool, but I find helm charts to me tedious to setup are you using them often?
Yeah, it can be a bit confusing when starting, but follow a YouTube course. Its really simple in the basics, but immensely powerful. Its a must know if you want to work as a cloud native / platform engineer.
Kustomize and Helm solve this already
ARGOCD..
the templating is the easy 20% - the part that kills homegrown platforms is day 2: who owns the golden path when someone needs an escape hatch, and how you push a change to 40 apps without a week of manual yaml edits. at your scale i'd resist building a tool and just run kustomize overlays over a base you actually maintain - you get the copy-and-tweak workflow without a bespoke platform to keep alive. build the tool the day copying a template stops being the bottleneck, not before.
Just use some gitops. ArgoCD, helm, GitHub (which you already use). You can create a “base helm” and inherit all your apps from it, therefore you code the base orchestration once for your needs. On top of that, you can ai code a ui that let your spin quick, but you don’t have to write the whole orchestration and versioning layer (rollouts, resource allocation, etc)
AI slop?