Add an option to show the content in two different pages.

Author: lucastigera

calico/operations/ebpf/install-opt2-auto.mdx

@@ -0,0 +1,15 @@
+---
+description: Install Calico in eBPF mode with auto configuration.
+---
+import InstallBPFGuide from '@site/calico/_includes/components/InstallBPFGuide';
+
+# Auto configuration
+<InstallBPFGuide installMode="auto"/>
+
+
+## Next steps
+
+**Recommended**
+
+- [Learn more about eBPF](use-cases-ebpf.mdx)
+- [Debug eBPF policies](../../network-policy/policy-rules/log-rules.mdx)

calico/operations/ebpf/install-opt2-manual.mdx

@@ -0,0 +1,14 @@
+---
+description: Install Calico in eBPF mode.
+---
+import InstallBPFGuide from '@site/calico/_includes/components/InstallBPFGuide';
+
+# Manual configuration
+<InstallBPFGuide installMode="manual"/>
+
+## Next steps
+
+**Recommended**
+
+- [Learn more about eBPF](use-cases-ebpf.mdx)
+- [Debug eBPF policies](../../network-policy/policy-rules/log-rules.mdx)

calico/operations/ebpf/install-opt2.mdx

@@ -0,0 +1,116 @@
+---
+description: Install Calico in eBPF mode.
+---
+
+# Install in eBPF mode
+
+import EbpfValue from '@site/calico/_includes/content/_ebpf-value.mdx';
+
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+## Big picture
+
+Install the eBPF data plane during the initial installation of $[prodname].
+
+## Value
+
+<EbpfValue />
+
+## Concepts
+
+### eBPF
+
+eBPF (or "extended Berkeley Packet Filter"), is a technology that allows safe mini programs to be attached to various
+low-level hooks in the Linux kernel. eBPF has a wide variety of uses, including networking, security, and tracing.
+You’ll see a lot of non-networking projects leveraging eBPF, but for $[prodname] our focus is on networking,
+and in particular, pushing the networking capabilities of the latest Linux kernels to the limit.
+
+## Before you begin
+
+### Supported
+
+- x86-64
+- arm64 (little-endian)
+
+- Kubernetes datastore driver.
+
+- Distributions:
+
+  - Generic or kubeadm
+  - kOps
+  - OpenShift
+  - EKS
+  - AKS
+  - MKE
+
+- Linux distribution/kernel:
+
+  - Ubuntu 20.04.
+  - Red Hat v8.2 with Linux kernel v4.18.0-193 or above (Red Hat have backported the required features to that build).
+  - Another [supported distribution](../../getting-started/kubernetes/requirements.mdx) with Linux kernel v5.3 or above.
+
+- An underlying network fabric that allows VXLAN traffic between hosts. In eBPF mode, VXLAN is used to forward Kubernetes NodePort traffic.
+
+- IPv6
+
+Limitations:
+  
+  - IPIP is not supported ($[prodname] iptables does not support it either). VXLAN is the recommended overlay for eBPF mode.
+
+To enable IPv6 in eBPF mode, see [Configure dual stack or IPv6 only](../../networking/ipam/ipv6.mdx). You may be able to run with non-Calico IPAM. eks-cni is known to work.
+
+### Not supported
+
+- Other processor architectures.
+
+- etcd datastore driver.  The etcd datastore driver doesn't support watching Kubernetes services, which is required for some features in eBPF mode.
+
+- Distributions:
+
+  - GKE. This is because of an incompatibility with the GKE CNI plugin.
+
+  - RKE: eBPF mode cannot be enabled at install time because RKE doesn't provide
+    a stable address for the API server. However, by following [these instructions](enabling-ebpf.mdx),
+    it can be enabled as a post-install step.
+
+- Clusters with some eBPF nodes and some standard data plane and/or Windows nodes.
+- Floating IPs.
+- SCTP (either for policy or services).
+- Tagged VLAN devices.
+
+### Performance
+
+For best pod-to-pod performance, we recommend using an underlying network that doesn't require Calico to use an overlay. For example:
+
+- A cluster within a single AWS subnet.
+- A cluster using a compatible cloud provider's CNI (such as the AWS VPC CNI plugin).
+- An on-prem cluster with BGP peering configured.
+
+If you must use an overlay, we recommend that you use VXLAN, not IPIP. VXLAN has better performance than IPIP in
+eBPF mode due to various kernel optimisations.
+
+## How to
+
+To install in eBPF mode, we recommend using the Tigera Operator to install $[prodname] so these instructions
+use the operator. Installing $[prodname] normally consists of the following stages, which are covered by the
+main installation guides:
+
+- Create a cluster suitable to run $[prodname].
+- Install the Tigera Operator (possibly via a Helm chart), and the associated Custom Resource Definitions.
+- Apply a set of Custom Resources to tell the operator what to install.
+- Wait for the operator to provision all the associated resources and report back via its status resource.
+
+There are two ways to install in eBPF mode with Operator: Auto and Manual configuration.
+
+import DocCardList from '@theme/DocCardList';
+import { useCurrentSidebarCategory } from '@docusaurus/theme-common';
+
+<DocCardList items={useCurrentSidebarCategory().items} />
+
+## Next steps
+
+**Recommended**
+
+- [Learn more about eBPF](use-cases-ebpf.mdx)
+- [Debug eBPF policies](../../network-policy/policy-rules/log-rules.mdx)

sidebars-calico.js

@@ -199,6 +199,18 @@ module.exports = {
             'operations/ebpf/use-cases-ebpf',
             'operations/ebpf/enabling-ebpf',
             'operations/ebpf/install',
+            {
+              type: 'category',
+              label: 'Install in eBPF mode',
+              link: {
+                type: 'doc',
+                id: 'operations/ebpf/install-opt2'
+              },
+              items: [
+                'operations/ebpf/install-opt2-auto',
+                'operations/ebpf/install-opt2-manual',
+              ],
+            },            
             'operations/ebpf/troubleshoot-ebpf',
           ],
         },