traefik-helm-chart VS renovate

helm chart Traefik Ingress

For an example, consider the NGINX Ingress Controller Helm Chart and the Traefik Ingress Controller Helm Chart. Both of these charts install an IngressController but they have their own set of features, configuration, and operation. While they do similar things, they are not the same. Rather than having to pull a bunch of yaml files from a github repo, you can execute a helm install after telling helm where the definition of the charts comes from for a given application. Helm will then go and fetch all the manifests contained in the chart and populate values into the manifest from its defined defaults merged with any values that you specify as an override (or option). If another version of the application comes out, rather than having to update everything, you can just run helm upgrade to update the release to a newer chart version (which may update the internal application code). If the chart version didn't change, but you need a newer release version, a lot of times this is handled by a version variable that you can specify. You just update that (either on the command line or in a values file) and run helm upgrade to change the manifests that get pushed and automatically your deployments will get updated.

Traefik was deployed using Traefik's chart (https://github.com/traefik/traefik-helm-chart). Reading the default values.yaml file, I understand that the Prometheus metrics endpoint is enabled by default. I can confirm that I see the metrics when I access the pod on port 9100/metrics/.

You can Just use the Traefik V2 Helm Chart https://github.com/traefik/traefik-helm-chart

You can find the CRDs in Traefik's helm chart repo

A thousand times, yes. I've wanted to write this same article. Thanks for saving me the time!

The industry is going to great lengths to avoid writing configuration in any ubiquitous imperative programming language. We're seeing the proliferation of hyper-specialized, clunky declarative languages with sub-par tooling and package ecosystems. In what world are templates acceptable code? I don't mean to pick on anything specific, but this[0] is the most recent example I've come across, and it's far from the most unreadable examples.

[0]: https://github.com/traefik/traefik-helm-chart/blob/master/tr...

I have Traefik 2 as my ingress controller acting as the reverse proxy, deployed via Helm. I am using the Bitnami Helm chart to deploy wordpress.

You can then use helm to remove the old traefik deployment and install from wherever you'd prefer. I used the official traefik helm. I made sure that I copied the values from /var/lib/rancher/k3s/server/manifests/traefik.yaml to my values file (retrieved from https://github.com/traefik/traefik-helm-chart/blob/master/traefik/values.yaml). Here I also added the helm operator ports.web.redirectTo: websecure (per u/soundwave_rk).

Traefik Helm chart has 402 stars, but the problem here is that 100 people can use it and they don't add stars since they don't log in to GitHub for it. I don't star Debian packages either.

I installed Traefik by helm. You'll need to install helm on the machine you're running kubectl on, then you can follow their instructions at https://github.com/traefik/traefik-helm-chart to install.

This month, I gave a talk with my Zenika colleague Lise at the DevoxxFR conference about Renovate and Dependabot, two great tools to help you automatize and upgrade your dependencies.

There is no built-in Renovate Bot on a self-hosted GitLab. What can we do to set it up and enjoy all the benefits of automatic dependency updates?

> Yes, it is awesome until you have to sysadmin it, apply updates, patch it, fix security holes, etc. I am not saying all self-hosted solutions are like that. There are exceptions. However, the majority of open-source self-hosted solutions require a lot of extra work.

I'm currently self-hosting 10 different applications on my local server, which represents everything I've ever seen that looked fun or useful to me. Every one of them had a Docker image with an example compose file, which means updating them just requires periodically running Renovate [0] on the repo that stores all my compose files and then running a script that docker compose pulls the updates. It takes maybe 10 minutes every other week, and is actually kinda fun.

It helps that all the apps are only accessible from within my VPN, so I'm not too worried about fixing security updates within a tiny time window.

[0] https://github.com/renovatebot/renovate

This is a big deal! Where did you read this? I found:

https://github.com/renovatebot/renovate/discussions/26917

Renovate is an automated dependency management tool that can be used to keep your dependencies up-to-date. It can be configured to automatically create pull requests to update your dependencies, and it supports a wide range of package managers and platforms.

To get started with Mend Renovate, the comprehensive official documentation provides detailed instructions on installation, configuration, and best practices. Additionally, the Mend Renovate community forum offers a platform for users to connect, share experiences, and access the collective knowledge base.

It is a good practice to keep software up to date. To track changes in upstream software, we can utilize automatic dependency tracking systems such as Dependabot or Renovate. This is a broad topic and requires a separate article to be covered. If you would like to read about it, please vote in the comments section below.

So do other forges: I have Renovate [0] set up on my self-hosted Forgejo and it's worked great so far.

[0] https://github.com/renovatebot/renovate

You can ease some of the burden for yourself though using tooling. If you are using GitHub, dependabot can be configured to make automatic PRs to your repo whenever there are dependencies to update. If you're not a GitHub user, you can use renovate which even supports self hosting.