You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With Kubernetes 1.16 there were some incompatible API changes that break addons, see e.g. #262.
I checked the Addons Documentation, and the source code of the existing addons, but I have not found any check for the Kubernetes version there.
To fix those addons and to support Kubernetes 1.16 as well as previous versions simultaneously, such a check would be needed. How would this be possible?
What's the current plan for the addons, should they be maintained or is using helm directly the preferred way?
The text was updated successfully, but these errors were encountered:
The hetzner-kube provided addons have the purpose to install these addons closer to the hetzner related cluster over the general setup. See hcloud-manager or custom rook tweaks etc.
So yes, there is a plan for supporting the necessary addons to make a smooth experience
To be honest, I don't have a clear idea at the moment. Another related topic is, that as of 1.15 the upgrade procedure from kubeadm got so straight forward, so it makes sense to introduce upgrade functionality and then we will have to deal with several versions anyways.
With Kubernetes 1.16 there were some incompatible API changes that break addons, see e.g. #262.
I checked the Addons Documentation, and the source code of the existing addons, but I have not found any check for the Kubernetes version there.
To fix those addons and to support Kubernetes 1.16 as well as previous versions simultaneously, such a check would be needed. How would this be possible?
What's the current plan for the addons, should they be maintained or is using
helm
directly the preferred way?The text was updated successfully, but these errors were encountered: