chore(helm)!: change iptables default mode to nft
#14326
Merged
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.
This change sets as a new default
nftfor theproxyInit.iptablesModeandiptablesModevalues in the linkerd-control-plane and linkerd2-cni helm charts. This doesn't imply any change in user-facing behavior.This was prompted by EKS with k8s 1.33 no longer supporting the iptables legacy mode.
Further testing in multiple platforms with different k8s versions revealed nft mode is now broadly supported.
Upgrading via Helm will apply the new default, unless legacy mode was explicitly set during the initial install.