4 ms·
Basically this is a helm chart. Which is one of the problems of k8s - a typical application consists of multiple services that need to be deployed together. In
by sandGorgon 7y ago
Basically this is a helm chart. Which is one of the problems of k8s - a typical application consists of multiple services that need to be deployed together.
In Docker Swarm, that's a Stack. K8s has no equivalent. So there's no answer to "how do i deploy/update my flask api and celery workers together"
- blairhudson 7y agoActually, Docker can now deploy stacks as a k8s “stack” resource: https://www.docker.com/blog/simplifying-kubernetes-with-docker-compose-and-friends/ https://www.docker.com/blog/simplifying-kubernetes-with-dock... This makes it especially easy for anyone transitioning from Docker Swarm to Kubernetes.
- sandGorgon 7y agoTrue. However the fact remains that k8s doesn't have a primitive here - so the toolsets (helm, docker stacks) have to manage it on a beat effort basis. In Swarm, the stack is an atomic unit. That's what Microsoft is trying to fix - the atomicity of an abstraction level that is higher than K8s Services. Not sure why they didnt do this as part of the k8s core committee process.
- cpuguy83 7y agoSwarm does not have a concept of a stack. This is purely client-side.
- fogetti 7y agoThanks for the link. I haven't heard about this before but it seems really useful.
- rumanator 7y ago> In Docker Swarm, that's a Stack. K8s has no equivalent. My take is that the equivalent in k8s is it's declarative management with configuration files. Just kubectl apply -f your.yaml and you're good to go.
- whazor 7y agoIdeally yes, however in practice a template engine is nice.
- ones_and_zeros 7y agoI don't think there is anything stopping you from bundling multiple services/deployments in the same helm chart. Many of the "curated" helm charts do it: https://github.com/helm/charts https://github.com/helm/charts