Let kubeadm manage cri-tools on Amazon Linux 2 #1701
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Marko Mudrinić <mudrinic.mare@gmail.com>
Signed-off-by: Marko Mudrinić <mudrinic.mare@gmail.com>
Signed-off-by: Marko Mudrinić <mudrinic.mare@gmail.com>
kubermatic-bot
added
release-note
This was referenced Dec 23, 2021
|
LGTM label has been added. Git tree hash: 30650b72aa8272068618d0fa7a3251be58cf6bff
|
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: moadqassem, xmudrii The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 this PR does / why we need it:
Before this PR, we were manually installing cri-tools 1.13.0 on Amazon Linux 2. Newer Kubernetes (kubeadm) versions are requiring cri-tools 1.19.0 which is conflicting with cri-tools 1.13.0. This is causing the cluster reconciliation/provisioning to fail.
With this PR, cri-tools is now installed automatically as a dependency of kubeadm. This way the package manager (
yum) will choose the proper version.If users are using the AssetConfiguration API (i.e. when they're not using packages to install kubeadm), we install the latest available cri-tools package using
yum.Does this PR introduce a user-facing change?:
/assign @moadqassem