Skip to content

Commit 8d91fd8

Browse files
committed
Split bpfInstallMode into two new fields: bpfNetworkBootstrap and kubeProxyManagement
1 parent b6140a0 commit 8d91fd8

3 files changed

Lines changed: 9 additions & 8 deletions

File tree

‎calico/_includes/components/InstallBPFGuide.js‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -286,7 +286,7 @@ EOF`}
286286

287287
<p>
288288
Edit the file in your editor of choice and find the <code>Installation</code> resource, which should be at the top of the file. To enable eBPF mode, we need to add a new <code>calicoNetwork</code> section inside the <code>spec</code> of the Installation resource, including the
289-
{props.installMode=="auto" && <span><code>bpfInstallMode</code> and the <code>linuxDataplane</code> fields. </span>}
289+
{props.installMode=="auto" && <span><code>bpfNetworkBootstrap</code>, <code>kubeProxyManagement</code> and the <code>linuxDataplane</code> fields. </span>}
290290
{props.installMode=="manual" &&<span> <code>linuxDataplane</code> field. </span>}
291291
For EKS Bottlerocket OS only, you should also add the <code>flexVolumePath</code> setting as shown below.
292292
</p>
@@ -302,7 +302,7 @@ metadata:
302302
spec:
303303
# Added calicoNetwork section with linuxDataplane field
304304
calicoNetwork:
305-
linuxDataplane: BPF${props.installMode === "auto" ? '\n bpfInstallMode: Auto' : ''}
305+
linuxDataplane: BPF${props.installMode === "auto" ? '\n bpfNetworkBootstrap: Enabled\n kubeProxyManagement: Enabled' : ''}
306306
307307
# EKS with Bottlerocket as node image only:
308308
# flexVolumePath: /var/lib/kubelet/plugins
@@ -326,7 +326,7 @@ spec: {}`}
326326
<p>
327327
If you already created the custom resources, you can switch your cluster over to eBPF mode by updating the installation resource. The operator will automatically roll out the change.
328328
</p>
329-
<CodeBlock language="bash">{`kubectl patch installation.operator.tigera.io default --type merge -p '{"spec":{"calicoNetwork":{"linuxDataplane":"BPF", ${props.installMode === "auto" ? '"bpfInstallMode":"Auto", ' : ''}"hostPorts":null}}}'`}</CodeBlock>
329+
<CodeBlock language="bash">{`kubectl patch installation.operator.tigera.io default --type merge -p '{"spec":{"calicoNetwork":{"linuxDataplane":"BPF", ${props.installMode === "auto" ? '"bpfNetworkBootstrap":"Enabled", "kubeProxyManagement":"Enabled", ' : ''}"hostPorts":null}}}'`}</CodeBlock>
330330
</Admonition>
331331

332332
<Heading

‎calico/operations/ebpf/enabling-ebpf.mdx‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -140,11 +140,11 @@ You can choose the automatic eBPF configuration if your cluster meets the follow
140140

141141
#### Configuring Installation CR
142142

143-
To enable eBPF mode with the auto configuration, set the `spec.calicoNetwork.bpfInstallMode` parameter in the operator's `Installation`
144-
resource to "Auto", and the `spec.calicoNetwork.linuxDataplane` parameter to "BPF".
143+
To enable eBPF mode with the auto configuration, set the `spec.calicoNetwork.bpfNetworkBootstrap` and `spec.calicoNetwork.kubeProxyManagement` parameters in the operator's `Installation`
144+
resource to "Enabled", and the `spec.calicoNetwork.linuxDataplane` parameter to "BPF".
145145

146146
```bash
147-
kubectl patch installation.operator.tigera.io default --type merge -p '{"spec":{"calicoNetwork":{"linuxDataplane":"BPF", "bpfInstallMode":"Auto"}}}'
147+
kubectl patch installation.operator.tigera.io default --type merge -p '{"spec":{"calicoNetwork":{"linuxDataplane":"BPF", "bpfNetworkBootstrap":"Enabled", "kubeProxyManagement":"Enabled"}}}'
148148
```
149149

150150
:::note

‎calico/operations/ebpf/install.mdx‎

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -124,7 +124,7 @@ To do this, instead of applying `custom-resources.yaml` directly using kubectl c
124124
```
125125

126126
Edit the file and find the `Installation` resource, (usually at the top).
127-
To enable eBPF mode, add a `calicoNetwork` section inside the `spec` with the `bpfInstallMode` and `linuxDataplane` fields.
127+
To enable eBPF mode, add a `calicoNetwork` section inside the `spec` with the `bpfNetworkBootstrap`, `kubeProxyManagement`, and `linuxDataplane` fields.
128128
For EKS Bottlerocket, also include the `flexVolumePath` field.
129129

130130
For example:
@@ -140,7 +140,8 @@ spec:
140140
# Added calicoNetwork section with linuxDataplane field
141141
calicoNetwork:
142142
linuxDataplane: BPF
143-
bpfInstallMode: Auto
143+
bpfNetworkBootstrap: Enabled
144+
kubeProxyManagement: Enabled
144145

145146
# EKS with Bottlerocket as node image only:
146147
# flexVolumePath: /var/lib/kubelet/plugins

0 commit comments

Comments
 (0)