awesome-home-kubernetes VS watchtower

Also check out the awesome kubernetes@home repo where many homelabbers share their configs.

Sorry I'm not familiar with this. Are you referring to this?

https://github.com/k8s-at-home/awesome-home-kubernetes https://github.com/k8s-at-home/template-cluster-k3s

To see it in action be sure to check out my repository or the many others here.

Make it usable and link to the best place with k3s in action: https://github.com/k8s-at-home/awesome-home-kubernetes

Nice but I suggest going to https://github.com/k8s-at-home/awesome-home-kubernetes and learn from the best at this topic ;)

Check out Flux V2. It syncs a git repo with your cluster, allowing you to define your infrastructure as code. It will keep your cluster synced with your repo and detect changes. A number of example repos are Here and onedr0p did a example repo here There's many options for structuring folder, I'd recommend you have a look at a few repos and pick one you like. The linked template is a good start, as it helps avoid dependency hell with a crd folder that starts before the YAML that needs the crd defined. Many people on the awesome list also run ansible for full infrastructure as code. I spent a lot of time perfecting my setup to go from blank Ubuntu VM to my cluster with a few keystrokes. Running it in git also helps you be able to use things like renovate bot to keep versions up to date. As for namespaces, everyone had their own method, but about using kube-system. Also, keep a eye out for services that refuse to have their name space changed.

Related: https://github.com/containrrr/watchtower

> if you're using the docker image, upgrades are a breeze. Just bump the tag on the image, redeploy, and you're done.

Or you could just run Watchtower beside it and it will automatically update your docker containers. https://github.com/containrrr/watchtower If you are OK with automated updates.

So i primarily use containers on my local machine walled off from the internet, so it's not a big concern for me. Watchtower [1] is popular among home server users too which automatically updates containers to the latest image.

For production uses I think companies generally build their own containers. They would have a common base linux container and build the other containers based off that with a typical CI/CD pipeline. So if glibc is patched, it's probably patched in the base container and the others are then rebuilt. You don't have to patch each container individually, just the base. Production also minimizes the scope of containers with nothing installed except what's necessary so they have few dependencies.

[1] https://github.com/containrrr/watchtower

You can use Watchtower (https://containrrr.dev/watchtower/) that solves problem of manual pulling on VPS.

I checked https://containrrr.dev/watchtower/ and Arguments, but I don't understand where to attach that using portainer.

Again, there are options to automate some of the burden here by using tools such as Watchtower.

Have you ever deployed a Docker app on a server, but everytime you push a new version of your image to a Docker registry you need to manually restart your app? If you want to automate this restarting, this blog post is for you! I am now going to show you how you can do this with literally 1 simple command using Watchtower!