Skip to content

fix(k8s): fall back to legacy iptables - #2130

Open
stephenlclarke wants to merge 1 commit into
apple:mainfrom
stephenlclarke:fix/k8s-legacy-iptables
Open

fix(k8s): fall back to legacy iptables#2130
stephenlclarke wants to merge 1 commit into
apple:mainfrom
stephenlclarke:fix/k8s-legacy-iptables

Conversation

@stephenlclarke

Copy link
Copy Markdown

Type of Change

  • Bug fix
  • New feature
  • Breaking change
  • Documentation update

Motivation and Context

Closes #2120.

Probe the nftables backend during node preparation. When the node kernel cannot use it, select the available legacy iptables and ip6tables alternatives before applying the MSS rules. This also keeps subsequent Kubernetes components on the working backend.

Testing

  • Tested locally
  • Added/updated tests
  • Added/updated docs

Negative control with the former hard-coded nft path: the behavior fixture exited unsuccessfully and applied neither fallback nor MSS rules.

  • Shell behavior regressions for nft available/unavailable paths: 2/2 passed
  • Full non-integration suite: 758 tests passed
  • make fmt, make check, and git diff --check: passed
  • Commit signature: verified

Probe the nftables backend during node preparation and select the legacy iptables alternatives when the node kernel cannot use nftables. Apply the MSS rules through the selected system backend.

Fixes apple#2120
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: container k8s create fails when node preparation invokes iptables-nft

1 participant