4636be19a4
Static pods cannot use image pull secrets, so it's important that the
control plane images are not garbage-collected while we're doing a
Kubernetes upgrade otherwise the upgrade can fail.
Accordingly we want to disable garbage-collecting the images, then
pre-pull the new images, then do the actual K8s upgrade, then re-enable
image garbage collection.
Also included are a couple of fixes for places where we were using
subtly incorrect versions when retrieving the image list as part of
a multi-version upgrade.
TEST-PLAN:
PASS: Perform multi-version K8s upgrade on AIO-SX, ensure upgrade
passes and image garbage collection is disabled during the
upgrade and re-enabled when kubelet gets upgraded to the
final version.
PASS: Perform single-verison K8s upgrade on AIO-SX, ensure upgrade
passes and image garbage collection is disabled during the
upgrade and re-enabled when kubelet gets upgraded.
PASS: Perform single-version K8s upgrade on Standard lab, ensure
upgrade passes and image garbage collection is disabled on
each node during the upgrade and re-enabled when kubelet is
upgraded.
Closes-Bug: 2044492
Partial-Bug: 2044493
Change-Id: I358ae922e5c2c5c047806a1e6773b1d23a74cbd0
Signed-off-by: Chris Friesen <chris.friesen@windriver.com>
stx-puppet
The starlingx/stx-puppet repository handles the Puppet service1.
The Puppet service runs during bootstrap, and at every reboot, to provide a consistent configuration across the StarlingX system nodes.
This repository is not intended to be developed standalone, but rather as part of the StarlingX Source System, which is defined by the StarlingX manifest2.