feat: add support for custom kubeadm image repository #12128
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
What this PR does / why we need it:
This PR adds support for
kubeadm_image_repo
variable to utilize custom kubernetes core images, such askube-apiserver
andkube-proxy
.Previously, to achieve this same functionality, we would have to use a variable called
kube_image_repo
. However, this would have affected the entire ecosystem, includingnodelocaldns
,scheduler_plugins
, andcsi_attacher
. Instead, it is great for replacingregistry.k8s.io
, such as for air-gapped deployments.However, it is not suitable for changing the image repository for Kubernetes itself. And it is unnecessary to change the repository for each image such as
kube_apiserver
, because these core services are shipped with the Kubernetes version (e.g.v1.32.3
). Also, their existence is derived fromkubeadm
, so manual configuration is unnecessary. Therefore, the core of this PR is to add the ability to replace only the image repository used bykubeadm
.Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: