Updates to automatically installed workloads

[rombert]

Hi,

I started looking into this project and looks like a perfect fit for my needs :-)

I like managing various non-core Kubernetes workloads via GitOps with Flux 2 so I cut down on some of the add-ons so I can manage them myself:

  enable_cert_manager = false
  enable_metrics_server = false
  ingress_controller = "none"

There are still a couple of workloads which I view as either core ( e.g. coredns ) or Hetzner-specific so I'm leaving them managed by kube-hetzner:

• deploy/coredns
• deploy/hcloud-cloud-controller-manager
• deploy/hcloud-csi-controller
• deploy/system-upgrade-controller
• daemonset/hcloud-csi-node
• daemonset/kured

What is not clear to me is how these workloads get upgraded to the latest version, can anyone please clarify that?

[mysticaltech]

@rombert That is a great question that we perhaps did not answer clearly enough in the readme. Basically, when you deploy your cluster, a kustomization backup file gets created locally, and you can use that to update the above components. You also have other components that you need to update via helm, you can see them by looking at the rancher helm CRDs, just grep the kubectl get crds for helm.

[mrclrchtr]

Ah ok, thank you very much!
That's more or less the way I go with traefik, for example.

However, Hetzner CCM is not installed via helm, for example, is it? The same as CSI, Kured etc.

[mysticaltech]

@mrclrchtr Please, if you could tell me how you do it for traefik it would be great. I'm interested in real world use cases.

About the rest of the component not managed by helm, the method is explained here, basically you need to edit the kustomization. See the corresponding readme section.

[mysticaltech]

When you sort this out, if you could find the time to submit a PR with an added example in the examples section of the readme of how to upgrade all individual component, it would be beyond awesome!

[mrclrchtr]

@mysticaltech It's quite simple for traefik:
ArgoCD is responsible for deployments (in the correct version). Take the values.yaml (which is generated with export_values = true) and the traefik helm chart to "deploy" with ArgoCD. In reality, only ArgoCD labels are written to the components.

For version upgrades I monitor the ArgoCD application yamls with RenovateBot. As soon as a new version is released a PR is created and after the merge ArgoCD deploys the new version.

This is therefore only possible due to the use of the Helm Chart. Maybe we can also deploy CCM etc. via helm...?

If I find a good solution for the other components, I'll let you know.

[mysticaltech]

@mrclrchtr Thanks for the details, it's a beautiful system you got there! I think indeed that it would be best that we move all of our components to helm. PR welcome even if just for one of them that you use 🙏 We will definitely go in that direction in the future.