Hi, On Wed, Mar 03, Johannes Kastl wrote:
Hi Robert, Richard,
On 01.03.21 at 14:37 Robert Munteanu wrote:
How would you handle the tasks that kubic does not perform out of the box?
Is there any specific reason why kubic does not handle these miniscule updates? Other than no one having time to implement it this far?
Exactly this, nobody had time to look at how this could be done and implement it.
In other words, what would be needed to actually automatically upgrade your containers from 1.19.4 to 1.19.7 once the underlying packages do this version step?
This would be the first step on the way to an implementation ;) But this is not as simple as it sounds like, since there are different ways to deploy and configure kubernetes on Kubic. Anyways, the upgrade of the containers from 1.19.4 to 1.19.7 has to be done with "kubeadm upgrade". Even if it is only a minor update. Question is how to orchestrate this calls. If you use kubic-control, it would be a simple call and salt would take care of the rest. If the deployment was done manually with kubeadm, you need to login manually on every node and upgrade if I don't miss another way. Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany Managing Director: Felix Imendoerffer (HRB 36809, AG Nürnberg)