docs: note bridge-nf-call-iptables requirement for Connect #6607
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.
For #6580
The Connect integration uses bridge networking and iptables to send traffic between containers. But the RedHat family of Linux distros sets some of the kernel tunables we need to be optimized for VMs rather than containers. We can document this behavior for now and consider better operator feedback for pre-flight checking later.
Note that arguably this is something that should get fixed in the upstream CNI plugins, but changing this kernel tunable silently sounds problematic from Nomad's perspective as it would probably break workloads running with the QEMU task driver.