From 306ab8076eb5b2669d108983bd5b09e9a7e00a27 Mon Sep 17 00:00:00 2001 From: Christopher Tauchen Date: Tue, 17 Dec 2024 15:54:33 +0000 Subject: [PATCH 1/2] Changes to minikube command --- calico/getting-started/kubernetes/minikube.mdx | 2 +- .../version-3.26/getting-started/kubernetes/minikube.mdx | 2 +- .../version-3.27/getting-started/kubernetes/minikube.mdx | 2 +- .../version-3.28/getting-started/kubernetes/minikube.mdx | 2 +- .../version-3.29/getting-started/kubernetes/minikube.mdx | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/calico/getting-started/kubernetes/minikube.mdx b/calico/getting-started/kubernetes/minikube.mdx index b2f7288864..1aff9ec191 100644 --- a/calico/getting-started/kubernetes/minikube.mdx +++ b/calico/getting-started/kubernetes/minikube.mdx @@ -39,7 +39,7 @@ Enabling preinstalled $[prodname] might be the quickest way for testing. However ::: ```bash -minikube start --network-plugin=cni --cni=calico +minikube start --cni=calico ``` diff --git a/calico_versioned_docs/version-3.26/getting-started/kubernetes/minikube.mdx b/calico_versioned_docs/version-3.26/getting-started/kubernetes/minikube.mdx index b2f7288864..1aff9ec191 100644 --- a/calico_versioned_docs/version-3.26/getting-started/kubernetes/minikube.mdx +++ b/calico_versioned_docs/version-3.26/getting-started/kubernetes/minikube.mdx @@ -39,7 +39,7 @@ Enabling preinstalled $[prodname] might be the quickest way for testing. However ::: ```bash -minikube start --network-plugin=cni --cni=calico +minikube start --cni=calico ``` diff --git a/calico_versioned_docs/version-3.27/getting-started/kubernetes/minikube.mdx b/calico_versioned_docs/version-3.27/getting-started/kubernetes/minikube.mdx index b2f7288864..1aff9ec191 100644 --- a/calico_versioned_docs/version-3.27/getting-started/kubernetes/minikube.mdx +++ b/calico_versioned_docs/version-3.27/getting-started/kubernetes/minikube.mdx @@ -39,7 +39,7 @@ Enabling preinstalled $[prodname] might be the quickest way for testing. However ::: ```bash -minikube start --network-plugin=cni --cni=calico +minikube start --cni=calico ``` diff --git a/calico_versioned_docs/version-3.28/getting-started/kubernetes/minikube.mdx b/calico_versioned_docs/version-3.28/getting-started/kubernetes/minikube.mdx index b2f7288864..1aff9ec191 100644 --- a/calico_versioned_docs/version-3.28/getting-started/kubernetes/minikube.mdx +++ b/calico_versioned_docs/version-3.28/getting-started/kubernetes/minikube.mdx @@ -39,7 +39,7 @@ Enabling preinstalled $[prodname] might be the quickest way for testing. However ::: ```bash -minikube start --network-plugin=cni --cni=calico +minikube start --cni=calico ``` diff --git a/calico_versioned_docs/version-3.29/getting-started/kubernetes/minikube.mdx b/calico_versioned_docs/version-3.29/getting-started/kubernetes/minikube.mdx index de0f64dbb1..1aff9ec191 100644 --- a/calico_versioned_docs/version-3.29/getting-started/kubernetes/minikube.mdx +++ b/calico_versioned_docs/version-3.29/getting-started/kubernetes/minikube.mdx @@ -39,7 +39,7 @@ Enabling preinstalled $[prodname] might be the quickest way for testing. However ::: ```bash -minikube start --cni="calico" +minikube start --cni=calico ``` From 5e0507868ce8e6dbf45d0d1bb625fc04ae1eab90 Mon Sep 17 00:00:00 2001 From: Christopher Tauchen Date: Tue, 17 Dec 2024 16:03:48 +0000 Subject: [PATCH 2/2] Fix indentation --- .../getting-started/kubernetes/minikube.mdx | 38 +++++++++---------- .../getting-started/kubernetes/minikube.mdx | 38 +++++++++---------- .../getting-started/kubernetes/minikube.mdx | 38 +++++++++---------- .../getting-started/kubernetes/minikube.mdx | 38 +++++++++---------- .../getting-started/kubernetes/minikube.mdx | 38 +++++++++---------- 5 files changed, 95 insertions(+), 95 deletions(-) diff --git a/calico/getting-started/kubernetes/minikube.mdx b/calico/getting-started/kubernetes/minikube.mdx index 1aff9ec191..35054560f9 100644 --- a/calico/getting-started/kubernetes/minikube.mdx +++ b/calico/getting-started/kubernetes/minikube.mdx @@ -47,40 +47,40 @@ minikube start --cni=calico 1. Start your minikube cluster with one control plane node using the following command. -:::note + :::note -If `192.168.0.0/16` is already in use within your network you must select a different pod network CIDR, by replacing `192.168.0.0/16` in the following command. + If `192.168.0.0/16` is already in use within your network you must select a different pod network CIDR, by replacing `192.168.0.0/16` in the following command. -::: + ::: -```bash -minikube start --cni=false --network-plugin=cni --extra-config=kubeadm.pod-network-cidr=192.168.0.0/16 --subnet=172.16.0.0/24 -``` + ```bash + minikube start --cni=false --network-plugin=cni --extra-config=kubeadm.pod-network-cidr=192.168.0.0/16 --subnet=172.16.0.0/24 + ``` 2. Install the Tigera $[prodname] operator and custom resource definitions. -```bash -kubectl create -f $[manifestsUrl]/manifests/tigera-operator.yaml -``` + ```bash + kubectl create -f $[manifestsUrl]/manifests/tigera-operator.yaml + ``` -:::note + :::note -Due to the large size of the CRD bundle, `kubectl apply` might exceed request limits. Instead, use `kubectl create` or `kubectl replace`. + Due to the large size of the CRD bundle, `kubectl apply` might exceed request limits. Instead, use `kubectl create` or `kubectl replace`. -::: + ::: 3. Install $[prodname] by creating the necessary custom resource. For more information on configuration options available in this manifest, see [the installation reference](../../reference/installation/api.mdx). -:::note + :::note -Before creating this manifest, read its contents and make sure its settings are correct for your environment. For example, -if you have replaced `pod-network-cidr` you must change it in this file as well. + Before creating this manifest, read its contents and make sure its settings are correct for your environment. For example, + if you have replaced `pod-network-cidr` you must change it in this file as well. -::: + ::: -```bash -kubectl create -f $[manifestsUrl]/manifests/custom-resources.yaml -``` + ```bash + kubectl create -f $[manifestsUrl]/manifests/custom-resources.yaml + ``` diff --git a/calico_versioned_docs/version-3.26/getting-started/kubernetes/minikube.mdx b/calico_versioned_docs/version-3.26/getting-started/kubernetes/minikube.mdx index 1aff9ec191..35054560f9 100644 --- a/calico_versioned_docs/version-3.26/getting-started/kubernetes/minikube.mdx +++ b/calico_versioned_docs/version-3.26/getting-started/kubernetes/minikube.mdx @@ -47,40 +47,40 @@ minikube start --cni=calico 1. Start your minikube cluster with one control plane node using the following command. -:::note + :::note -If `192.168.0.0/16` is already in use within your network you must select a different pod network CIDR, by replacing `192.168.0.0/16` in the following command. + If `192.168.0.0/16` is already in use within your network you must select a different pod network CIDR, by replacing `192.168.0.0/16` in the following command. -::: + ::: -```bash -minikube start --cni=false --network-plugin=cni --extra-config=kubeadm.pod-network-cidr=192.168.0.0/16 --subnet=172.16.0.0/24 -``` + ```bash + minikube start --cni=false --network-plugin=cni --extra-config=kubeadm.pod-network-cidr=192.168.0.0/16 --subnet=172.16.0.0/24 + ``` 2. Install the Tigera $[prodname] operator and custom resource definitions. -```bash -kubectl create -f $[manifestsUrl]/manifests/tigera-operator.yaml -``` + ```bash + kubectl create -f $[manifestsUrl]/manifests/tigera-operator.yaml + ``` -:::note + :::note -Due to the large size of the CRD bundle, `kubectl apply` might exceed request limits. Instead, use `kubectl create` or `kubectl replace`. + Due to the large size of the CRD bundle, `kubectl apply` might exceed request limits. Instead, use `kubectl create` or `kubectl replace`. -::: + ::: 3. Install $[prodname] by creating the necessary custom resource. For more information on configuration options available in this manifest, see [the installation reference](../../reference/installation/api.mdx). -:::note + :::note -Before creating this manifest, read its contents and make sure its settings are correct for your environment. For example, -if you have replaced `pod-network-cidr` you must change it in this file as well. + Before creating this manifest, read its contents and make sure its settings are correct for your environment. For example, + if you have replaced `pod-network-cidr` you must change it in this file as well. -::: + ::: -```bash -kubectl create -f $[manifestsUrl]/manifests/custom-resources.yaml -``` + ```bash + kubectl create -f $[manifestsUrl]/manifests/custom-resources.yaml + ``` diff --git a/calico_versioned_docs/version-3.27/getting-started/kubernetes/minikube.mdx b/calico_versioned_docs/version-3.27/getting-started/kubernetes/minikube.mdx index 1aff9ec191..35054560f9 100644 --- a/calico_versioned_docs/version-3.27/getting-started/kubernetes/minikube.mdx +++ b/calico_versioned_docs/version-3.27/getting-started/kubernetes/minikube.mdx @@ -47,40 +47,40 @@ minikube start --cni=calico 1. Start your minikube cluster with one control plane node using the following command. -:::note + :::note -If `192.168.0.0/16` is already in use within your network you must select a different pod network CIDR, by replacing `192.168.0.0/16` in the following command. + If `192.168.0.0/16` is already in use within your network you must select a different pod network CIDR, by replacing `192.168.0.0/16` in the following command. -::: + ::: -```bash -minikube start --cni=false --network-plugin=cni --extra-config=kubeadm.pod-network-cidr=192.168.0.0/16 --subnet=172.16.0.0/24 -``` + ```bash + minikube start --cni=false --network-plugin=cni --extra-config=kubeadm.pod-network-cidr=192.168.0.0/16 --subnet=172.16.0.0/24 + ``` 2. Install the Tigera $[prodname] operator and custom resource definitions. -```bash -kubectl create -f $[manifestsUrl]/manifests/tigera-operator.yaml -``` + ```bash + kubectl create -f $[manifestsUrl]/manifests/tigera-operator.yaml + ``` -:::note + :::note -Due to the large size of the CRD bundle, `kubectl apply` might exceed request limits. Instead, use `kubectl create` or `kubectl replace`. + Due to the large size of the CRD bundle, `kubectl apply` might exceed request limits. Instead, use `kubectl create` or `kubectl replace`. -::: + ::: 3. Install $[prodname] by creating the necessary custom resource. For more information on configuration options available in this manifest, see [the installation reference](../../reference/installation/api.mdx). -:::note + :::note -Before creating this manifest, read its contents and make sure its settings are correct for your environment. For example, -if you have replaced `pod-network-cidr` you must change it in this file as well. + Before creating this manifest, read its contents and make sure its settings are correct for your environment. For example, + if you have replaced `pod-network-cidr` you must change it in this file as well. -::: + ::: -```bash -kubectl create -f $[manifestsUrl]/manifests/custom-resources.yaml -``` + ```bash + kubectl create -f $[manifestsUrl]/manifests/custom-resources.yaml + ``` diff --git a/calico_versioned_docs/version-3.28/getting-started/kubernetes/minikube.mdx b/calico_versioned_docs/version-3.28/getting-started/kubernetes/minikube.mdx index 1aff9ec191..35054560f9 100644 --- a/calico_versioned_docs/version-3.28/getting-started/kubernetes/minikube.mdx +++ b/calico_versioned_docs/version-3.28/getting-started/kubernetes/minikube.mdx @@ -47,40 +47,40 @@ minikube start --cni=calico 1. Start your minikube cluster with one control plane node using the following command. -:::note + :::note -If `192.168.0.0/16` is already in use within your network you must select a different pod network CIDR, by replacing `192.168.0.0/16` in the following command. + If `192.168.0.0/16` is already in use within your network you must select a different pod network CIDR, by replacing `192.168.0.0/16` in the following command. -::: + ::: -```bash -minikube start --cni=false --network-plugin=cni --extra-config=kubeadm.pod-network-cidr=192.168.0.0/16 --subnet=172.16.0.0/24 -``` + ```bash + minikube start --cni=false --network-plugin=cni --extra-config=kubeadm.pod-network-cidr=192.168.0.0/16 --subnet=172.16.0.0/24 + ``` 2. Install the Tigera $[prodname] operator and custom resource definitions. -```bash -kubectl create -f $[manifestsUrl]/manifests/tigera-operator.yaml -``` + ```bash + kubectl create -f $[manifestsUrl]/manifests/tigera-operator.yaml + ``` -:::note + :::note -Due to the large size of the CRD bundle, `kubectl apply` might exceed request limits. Instead, use `kubectl create` or `kubectl replace`. + Due to the large size of the CRD bundle, `kubectl apply` might exceed request limits. Instead, use `kubectl create` or `kubectl replace`. -::: + ::: 3. Install $[prodname] by creating the necessary custom resource. For more information on configuration options available in this manifest, see [the installation reference](../../reference/installation/api.mdx). -:::note + :::note -Before creating this manifest, read its contents and make sure its settings are correct for your environment. For example, -if you have replaced `pod-network-cidr` you must change it in this file as well. + Before creating this manifest, read its contents and make sure its settings are correct for your environment. For example, + if you have replaced `pod-network-cidr` you must change it in this file as well. -::: + ::: -```bash -kubectl create -f $[manifestsUrl]/manifests/custom-resources.yaml -``` + ```bash + kubectl create -f $[manifestsUrl]/manifests/custom-resources.yaml + ``` diff --git a/calico_versioned_docs/version-3.29/getting-started/kubernetes/minikube.mdx b/calico_versioned_docs/version-3.29/getting-started/kubernetes/minikube.mdx index 1aff9ec191..35054560f9 100644 --- a/calico_versioned_docs/version-3.29/getting-started/kubernetes/minikube.mdx +++ b/calico_versioned_docs/version-3.29/getting-started/kubernetes/minikube.mdx @@ -47,40 +47,40 @@ minikube start --cni=calico 1. Start your minikube cluster with one control plane node using the following command. -:::note + :::note -If `192.168.0.0/16` is already in use within your network you must select a different pod network CIDR, by replacing `192.168.0.0/16` in the following command. + If `192.168.0.0/16` is already in use within your network you must select a different pod network CIDR, by replacing `192.168.0.0/16` in the following command. -::: + ::: -```bash -minikube start --cni=false --network-plugin=cni --extra-config=kubeadm.pod-network-cidr=192.168.0.0/16 --subnet=172.16.0.0/24 -``` + ```bash + minikube start --cni=false --network-plugin=cni --extra-config=kubeadm.pod-network-cidr=192.168.0.0/16 --subnet=172.16.0.0/24 + ``` 2. Install the Tigera $[prodname] operator and custom resource definitions. -```bash -kubectl create -f $[manifestsUrl]/manifests/tigera-operator.yaml -``` + ```bash + kubectl create -f $[manifestsUrl]/manifests/tigera-operator.yaml + ``` -:::note + :::note -Due to the large size of the CRD bundle, `kubectl apply` might exceed request limits. Instead, use `kubectl create` or `kubectl replace`. + Due to the large size of the CRD bundle, `kubectl apply` might exceed request limits. Instead, use `kubectl create` or `kubectl replace`. -::: + ::: 3. Install $[prodname] by creating the necessary custom resource. For more information on configuration options available in this manifest, see [the installation reference](../../reference/installation/api.mdx). -:::note + :::note -Before creating this manifest, read its contents and make sure its settings are correct for your environment. For example, -if you have replaced `pod-network-cidr` you must change it in this file as well. + Before creating this manifest, read its contents and make sure its settings are correct for your environment. For example, + if you have replaced `pod-network-cidr` you must change it in this file as well. -::: + ::: -```bash -kubectl create -f $[manifestsUrl]/manifests/custom-resources.yaml -``` + ```bash + kubectl create -f $[manifestsUrl]/manifests/custom-resources.yaml + ```