BPF docs - Add a note about IPVS and MKE docs to 3.28 #1634
Conversation
✅ Deploy Preview for calico-docs-preview-next ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview succeeded!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
| @@ -161,6 +161,11 @@ To re-enable it: | |||
| ```bash | |||
| kubectl patch networks.operator.openshift.io cluster --type merge -p '{"spec":{"deployKubeProxy": true}}' | |||
| ``` | |||
| :::note | |||
|
|
|||
| If you are running kube-proxy in IPVS mode, switch to IPTables mode before disabling. | |||
There was a problem hiding this comment.
yes, switch IPTable to iptables
There was a problem hiding this comment.
should it be part of ### Configure kube-proxy ?
There was a problem hiding this comment.
Its part of configure kube-proxy section.
|
@sridhartigera Can you provide some context here? Links to tickets, say? |
@ctauchen we don't support migrating from IPVS mode to eBPF dataplane. We have seen few users trying this. Hence it will be better to call this out explicitly. |
sridhartigera
changed the title
| @@ -42,6 +42,7 @@ and in particular, pushing the networking capabilities of the latest Linux kerne | |||
| **Unsupported platforms** | |||
|
|
|||
| - GKE | |||
| - MKE | |||
There was a problem hiding this comment.
If we're removing support for MKE, do we not need to remove from other areas? See Line 170 in enabling-ebpf.mdx. I can't make any sense of this. If there's a qualification, this must be made explicit.
There was a problem hiding this comment.
Sorry. That was a mistake. we are not removing support for MKE. Reverted ^^
Product Version(s):
Issue:
Link to docs preview:
SME review:
DOCS review:
Additional information:
Merge checklist: