skaffold VS helm

Skaffold + Docker Dekstop Kubernetes works really well for me. My company's main codebase has ~7 services, service discovery works by DNS (k8s services), everything is super composable. Obviously, since we're a kubernetes focused company so I'm biased, but Skaffold is fantastic.

Skaffold is an open source project started by a Google engineer after suffering the pain of cloud native Kubernetes deployments. It’s effectively a command-line tool that automates the build, push, and deploy steps for Kubernetes applications.

Skaffold

This article only scraches the surface of what skaffold is capable of! You can find tons examples in the official github repository

Author here. Tilt is great.

After minikube I wrote skaffold, which is a closer alternative to docker compose for Kubernetes with file watching and automated rebuilds and syncs.

https://skaffold.dev

I built something like this in Go a few years ago but it reloads your infrastructure when it changes, recompiles your code when it needs to, and syncs static files or interpreted files to wherever your app is running (desktop or cloud). Think of it like docker-compose but with file watching + sync + smart rebuilds. https://skaffold.dev/

DevSpace sounds pretty interesting and seems to address the issue of migrations pretty clearly, whether with hooks or just doing something like devspace enter python manage.py migrate in the Python example. It seems like doing Django migrations with Skaffold involves setting up a Pod or Job solely for this purpose. It doesn't sound like there is functionality, or plans to add it, to Skaffold for running custom commands in the Pod: https://github.com/GoogleContainerTools/skaffold/issues/4179.

I installed nginx-ingress using helm, which came down to the following commands:

That's a really nice documentation page, however what's missing in my eyes is an example or two for each parameter in YAML format. Personally, when attempting to use Docker Swarm, things like that were immensely useful, even more so for Hashicorp Nomad and its somewhat niche HCL.

I know that people like to use something like Kustomize (https://kustomize.io/) and Helm (https://helm.sh/) at least last i checked, but it's also really nice to be able to read up on everything without necessarily following tutorials and such.

For example, with Docker Swarm, if i want to change how restarts would be handled, i have a really easy reference available: https://docs.docker.com/compose/compose-file/compose-file-v3...

But with Kubernetes, in the first linked page i find a short description (just scroll down a bit or CTRL+F "restartPolicy") which doesn't offer further parameters: https://kubernetes.io/docs/reference/generated/kubernetes-ap...

To its credit, there is a link to another page as well which contains more information: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifec...

That said, usability wise i'd have to spend more time to figure out how to get my containers/pods restarting just once every 1 minute as opposed to whatever the default is (say, low end cluster with limited resources) with Kubernetes instead of other technologies, due to this difference.

Helm - https://helm.sh

In most cases, you will need to update your Kubernetes manifest YAMLs or Helm charts (Deployment, Service, or Pod) and apply those changes either directly into the Production or Staging or into the Test environment.

helm for package management (with argo)

You can check https://helm.sh/ for the helm application it's a software manager for kubernetes.

Pulumi is an IaaC tool https://www.pulumi.com/ Helm is a Kubernetes package manager https://helm.sh/ ArgoCD is a continuous delivery tool for Kubernetes https://argo-cd.readthedocs.io/en/stable/

Helm charts are the type of deployment I do (mostly). This is a way to obstract the entire deployment to a simple configuration. https://helm.sh/