From 981876512f07052aea6120799a8b8c68bace10eb Mon Sep 17 00:00:00 2001 From: frozenprocess <54559947+frozenprocess@users.noreply.github.com> Date: Wed, 8 Oct 2025 16:53:22 -0700 Subject: [PATCH] docs: update Calico - Added some info for Kubeprsim - Fixed an installation issue --- .../network/deploying-calico.md | 106 ++++++++---------- .../network/deploying-calico.md | 106 ++++++++---------- 2 files changed, 98 insertions(+), 114 deletions(-) diff --git a/website/content/v1.11/kubernetes-guides/network/deploying-calico.md b/website/content/v1.11/kubernetes-guides/network/deploying-calico.md index 122d9c71aeb..203dc0d35dd 100644 --- a/website/content/v1.11/kubernetes-guides/network/deploying-calico.md +++ b/website/content/v1.11/kubernetes-guides/network/deploying-calico.md @@ -39,14 +39,48 @@ kubectl create -f https://docs.tigera.io/calico/latest/manifests/tigera-operator ### Configuring Calico Networking -Calico has a pluggable dataplane architecture that lets you choose the networking technology based on your use case. You can configure the dataplane by setting the `linuxDataplane` key in the installation manifest. +Calico has a pluggable dataplane architecture that lets you choose the networking technology based on your use case. Networking technology is the backend that allows your nodes to move a packet from a source or destination to your Kubernetes resources. > **Note** If you like to learn more about the available Calico configurations [checkout this document](https://docs.tigera.io/calico/latest/reference/installation/api). {{< tabpane text=true >}} +{{% tab header="NFTables" %}} + +> **Note**: Calico also supports iptables backend, if you wish to run Calico in iptables mode change `linuxdataplane` value to `Iptables`. + +Use the following command to run Calico with NFTables backend. + +```bash +kubectl create -f -< **Note** If you’d like to learn more about the available Calico configurations, [checkout this document](https://docs.tigera.io/calico/latest/reference/installation/api). - In eBPF mode, Calico completely replaces the need for kube-proxy by programming all networking logic via eBPF programs. Before disabling kube-proxy, however, you need to ensure that Calico components can reach the API server. This can be done by creating a `kubernetes-services-endpoint` ConfigMap. -Store the following YAML template in a file (e.g., `endpoint.yaml`), and replace and with your Kubernetes API server host and port. -If [KubePrism]({{< relref "../configuration/kubeprism" >}}) is enabled (which is the default), use `localhost` as the API server host and `7445` as the port. +> **Note**: In this part we assume you are using [KubePrism]({{< relref "../configuration/kubeprism" >}}) (which is enabled by the default). -```yaml +```bash +kubectl create -f -<' - KUBERNETES_SERVICE_PORT: '' -``` - -After editing the file, apply it using: - -```bash -kubectl create -f endpoint.yaml + KUBERNETES_SERVICE_HOST: 'localhost' + KUBERNETES_SERVICE_PORT: '7445' +EOF ``` You can now safely disable `kube-proxy` by using the following command: @@ -104,49 +131,14 @@ spec: calicoNetwork: bgp: Disabled linuxDataplane: BPF - cni: - ipam: - type: HostLocal - type: Calico - kubeletVolumePluginPath: None ---- -# Kubectl integration for Calico unique resources. -apiVersion: operator.tigera.io/v1 -kind: APIServer -metadata: - name: default -spec: {} -EOF -``` - -{{% /tab %}} -{{% tab header="NFTables" %}} - -Use the following command to run Calico with NFTables backend. - -```bash -kubectl create -f -< **Note** If you like to learn more about the available Calico configurations [checkout this document](https://docs.tigera.io/calico/latest/reference/installation/api). {{< tabpane text=true >}} +{{% tab header="NFTables" %}} + +> **Note**: Calico also supports iptables backend, if you wish to run Calico in iptables mode change `linuxdataplane` value to `Iptables`. + +Use the following command to run Calico with NFTables backend. + +```bash +kubectl create -f -< **Note** If you’d like to learn more about the available Calico configurations, [checkout this document](https://docs.tigera.io/calico/latest/reference/installation/api). - In eBPF mode, Calico completely replaces the need for kube-proxy by programming all networking logic via eBPF programs. Before disabling kube-proxy, however, you need to ensure that Calico components can reach the API server. This can be done by creating a `kubernetes-services-endpoint` ConfigMap. -Store the following YAML template in a file (e.g., `endpoint.yaml`), and replace and with your Kubernetes API server host and port. -If [KubePrism]({{< relref "../configuration/kubeprism" >}}) is enabled (which is the default), use `localhost` as the API server host and `7445` as the port. +> **Note**: In this part we assume you are using [KubePrism]({{< relref "../configuration/kubeprism" >}}) (which is enabled by the default). -```yaml +```bash +kubectl create -f -<' - KUBERNETES_SERVICE_PORT: '' -``` - -After editing the file, apply it using: - -```bash -kubectl create -f endpoint.yaml + KUBERNETES_SERVICE_HOST: 'localhost' + KUBERNETES_SERVICE_PORT: '7445' +EOF ``` You can now safely disable `kube-proxy` by using the following command: @@ -104,49 +131,14 @@ spec: calicoNetwork: bgp: Disabled linuxDataplane: BPF - cni: - ipam: - type: HostLocal - type: Calico - kubeletVolumePluginPath: None ---- -# Kubectl integration for Calico unique resources. -apiVersion: operator.tigera.io/v1 -kind: APIServer -metadata: - name: default -spec: {} -EOF -``` - -{{% /tab %}} -{{% tab header="NFTables" %}} - -Use the following command to run Calico with NFTables backend. - -```bash -kubectl create -f -<