On Mon, 2021-03-01 at 12:27 +0100, Robert Munteanu wrote:
On Mon, 2021-03-01 at 06:46 +0100, Thorsten Kukuk wrote:
Hi,
On Mon, Mar 01, Robert Munteanu wrote:
I could edit the DaemonSet manually, but I like the kubic unattended updates too much and would like to understand the contract related to minor version updates.
Should I file a bug or is this expected behaviour?
If you never upgrade your kubernetes cluster yourself then this is expected behaviour: we don't automatically upgrade deployed kubernetes clusters.
Sorry, I was incorrect in the description. I am talking about patch version updates, which kubic performs in an unattended manner. One of these updates broke one of the nodes in my cluster, and I want to understand if this is expected or not.
No idea how you deployed kubernetes, but you need to upgrade with that tool.
I used kubeadm as documented, and for minor updates I will do the same (e.g. 1.19.x to 1.20.x ). But this was a patch version update which should (IMO) be handled automatically by kubic.
Thanks, Robert
There is no mechanism in Kubernetes for magically changing your deployed containers to match your deployed binaries. Users need to update their deployed containers themselves aligned with their deployed binaries.