-
Bug
-
Resolution: Not a Bug
-
Undefined
-
None
-
4.14.0
-
No
-
False
-
Description of problem:
After control plane release upgrade, controlPlaneRelease field is set in the HostedCluster CR, upgrade release image, 'haproxy' container in the pod 'kube-apiserver-proxy-<node-name>' on the guest cluster isn't upgraded to new release image, it still uses old release image
Version-Release number of selected component (if applicable):
How reproducible:
always
Steps to Reproduce:
1. Create a cluster in 4.14.0-0.ci-2023-09-08-180504 2. do control plane release upgrade to 4.14.0-0.ci-2023-09-09-164300 3. do release upgrade to 4.14.0-0.ci-2023-09-09-000504 4. check containers/pods on the guest cluster
Actual results:
container 'haproxy' in the pod 'kube-apiserver-proxy-<node-name>' still uses old release image 4.14.0-0.ci-2023-09-08-180504
Expected results:
container 'haproxy' in the pod 'kube-apiserver-proxy-<node-name>' uses new release image 4.14.0-0.ci-2023-09-09-000504
Additional info: