OSSM_13620_nftables#111267
OSSM_13620_nftables#111267lhite8041 wants to merge 14 commits intoopenshift:service-mesh-docs-mainfrom
Conversation
|
/label merge-review-in-progress |
|
🤖 Fri May 08 19:00:50 - Prow CI generated the docs preview: |
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
|
@lhite8041 Thanks for the PR. We will need similar changes to the ambient mode as well. For your reference, please see https://github.com/istio-ecosystem/sail-operator/blob/main/docs/common/istio-nftables.adoc#install-in-ambient-mode |
|
|
||
| {SMProductShortName} relies on a packet-filtering backend to intercept and redirect application traffic to the service mesh data plane. Because {op-system-base-full} 10 removes the `iptables` framework, you must enable the `nativeNftables` parameter in your {istio} and `IstioCNI` resources. | ||
|
|
||
| Enabling this parameter allows the {istio} CNI plugin to detect the host's capabilities and use `nft` commands for redirection. In mixed clusters, the service mesh continues to use `iptables` on legacy nodes (such as {op-system-base-full} 9) while using `nftables` on {op-system-base-full} 10 nodes, ensuring a smooth transition during node migration. |
There was a problem hiding this comment.
Instead of saying "legacy" nodes, probably we can say "non-RHEL10" nodes.
| Enabling this parameter allows the {istio} CNI plugin to detect the host's capabilities and use `nft` commands for redirection. In mixed clusters, the service mesh continues to use `iptables` on legacy nodes (such as {op-system-base-full} 9) while using `nftables` on {op-system-base-full} 10 nodes, ensuring a smooth transition during node migration. | |
| Enabling this parameter allows the {istio} CNI plugin to detect the host's capabilities and use `nft` commands for redirection. In mixed clusters, the service mesh continues to use `iptables` on non-{op-system-base-full} 10 nodes while using `nftables` on {op-system-base-full} 10 nodes, ensuring a smooth transition during node migration. |
| [id="ossm-preparing-for-rhel-10-migration"] | ||
| = Preparing for Red Hat Enterprise Linux 10 migration | ||
| include::_attributes/common-attributes.adoc[] | ||
| :context: ossm-preparing-for-rhel-10-migration |
There was a problem hiding this comment.
Since we are talking about RHEL10 migration which covers areas beyond nftables, I'd like rzago@redhat.com to take a look at the updated content to see if we want to add something to this doc.
| @@ -0,0 +1,75 @@ | |||
| // Module included in the following assemblies: | |||
There was a problem hiding this comment.
After re-reviewing the updated files, I feel we can remove these two files (i.e., modules/ossm-migrate-to-nftables-rhel10-ambient.adoc and modules/ossm-migrate-to-nftables-rhel10-sidecar.adoc) all-together since we have mentioned the nftables config in the required files (i.e., modules/ossm-installing-istio-ambient-mode.adoc).
| [IMPORTANT] | ||
| ==== | ||
| Enable `nativeNftables` **before** you add {op-system-base-full} 10 nodes to your cluster. If this support is not enabled, service mesh components such as the `istio-cni` agent and the Ztunnel proxy will fail to initialize on the new nodes. | ||
| ==== |
There was a problem hiding this comment.
I think we can add a note specifically for Ambient mode as described here.
https://github.com/istio-ecosystem/sail-operator/blob/main/docs/common/istio-nftables.adoc#upgrade-in-ambient-mode
7946674 to
fdd5edd
Compare
|
@lhite8041: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
OSSM-13620: Support Native nftables in Istio (RHEL 10)
Version(s):
service-mesh-docs-main, service-mesh-docs-main-3.4, service-mesh-docs-main-3.3
Issue:
https://redhat.atlassian.net/browse/OSSM-13620
Link to docs preview:
QE review: