Fixed cp up --provider kind
kube-proxy issue on MacOS
#353
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's in this PR?
Fixed
cp up --provider kind
kube-proxy
issue onMacOS
which caused thekube-proxy
toCrashLoopBackoff
withopen /proc/sys/net/netfilter/nf_conntrack_max: permission denied
.Why?
kubernetes-sigs/kind#2240
I added a post-kind-create-clusters step to fix the issue for
MacOS
context where aConfigMap
change is enough.Additional context
Kind v0.11.1 is going to fix this issue, but upgrading breaks
bank-vaults
token issuer handling which is fixed inbank-vaults
v1.13.1, but upgradingbank-vaults
in Pipeline is a bigger effort so it is postponed.Checklist
User guide and development docs updated (if needed)Related Helm chart(s) updated (if needed)