3 ms·
It sounds really useful to install other people's stuff into Kubernetes. Is it useful to package your own applications for deployment into Kubernetes?
by bryanlarsen 10y ago
It sounds really useful to install other people's stuff into Kubernetes.
Is it useful to package your own applications for deployment into Kubernetes?
- slack 10y agoLots of folks have started integrating helm into their own internal deployment pipelines. Describing your own software as a helm chart gives you all the benefits of versioning, upgrades, rollbacks, lifecycle hooks, and release tracking. Also drastically cuts down on all the `kubectl {create,apply} -f ...` hacks that folks are using today. To get a sense of what that might look like, check out Lachlan Evenson's demo of a helm-based ci/cd pipline: https://www.youtube.com/watch?v=NVoln4HdZOY https://www.youtube.com/watch?v=NVoln4HdZOY
- charlieegan3 10y agoWhile this is a little light on the Helm specific details it's a good example. Thanks for sharing this.
- swozey 10y agoSay your application contained 5 nodejs containers, 5 postgres containers, 10 load balancers and 10 sets of secrets. You'd put those into a helm repo (git) and do a helm install and you'd have the app running and deployed as a named and versioned helm deployment, like wandering-goat. I plan on incorporating it into my CI/CD pipelines at some point but not quite there yet.