Bump k3s in go.mod to address issue with disabling kube-proxy #1462
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
brandond
force-pushed
the
fix_1455
branch
6 times, most recently
from
7ea42f4
to
e696eea
Compare
dereknola
approved these changes
Jul 29, 2021
Signed-off-by: Brad Davidson <brad.davidson@rancher.com>
Signed-off-by: Brad Davidson <brad.davidson@rancher.com>
galal-hussein
approved these changes
Jul 30, 2021
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.
Proposed Changes
Fix issue where kube-proxy static pod is started before the rke2-kube-proxy HelmChartConfig check completes
k3s-io/k3s@b1b5f72...5ab3590
Types of Changes
Bugfix
Verification
Start RKE2 with a rke2-kube-proxy HelmChartConfig present in your cluster; verify that the kube-proxy static pod is not started.
NOTE: The HelmChartConfig detection only works if the customization is present when upgrading an existing cluster. It will not be detected on new installations.
Linked Issues
Further Comments