Change Details

As stated in the parent task, we'd need to have the pause container at version 3.5+ for k8s 1.23. It is not clear how we have imported the current version on our registry, so we should probably add a specific config to production-images to be future proof. Steps: [x] Review the [[ https://github.com/kubernetes/kubernetes/blob/master/build/pause/CHANGELOG.md | CHANGELOG ]] and decide what version is needed. [ ] Add production-images build + pause image configuration. [ ] Build and publish the new image to the Docker registry (the new version should be compatible with the current 1.16 clusters but verify this as well).

As stated in the parent task, we'd need to have the pause container at version 3.5+ for k8s 1.23. It is not clear how we have imported the current version on our registry, so we should probably add a specific config to production-images to be future proof. Steps: [x] Review the [[ https://github.com/kubernetes/kubernetes/blob/master/build/pause/CHANGELOG.md | CHANGELOG ]] and decide what version is needed. [x] Add production-images build + pause image configuration. [x] Build and publish the new image to the Docker registry (the new version should be compatible with the current 1.16 clusters but verify this as well).

As stated in the parent task, we'd need to have the pause container at version 3.5+ for k8s 1.23. It is not clear how we have imported the current version on our registry, so we should probably add a specific config to production-images to be future proof. Steps: [x] Review the [[ https://github.com/kubernetes/kubernetes/blob/master/build/pause/CHANGELOG.md | CHANGELOG ]] and decide what version is needed. [ x] Add production-images build + pause image configuration. [ x] Build and publish the new image to the Docker registry (the new version should be compatible with the current 1.16 clusters but verify this as well).