Updates minikube commands

calico/getting-started/kubernetes/minikube.mdx

@@ -39,48 +39,48 @@ Enabling preinstalled $[prodname] might be the quickest way for testing. However
 :::
 
 ```bash
-minikube start --network-plugin=cni --cni=calico
+minikube start --cni=calico
 ```
 
 </TabItem>
 <TabItem label="Operator" value="Operator-1">
 
 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
+   ```
 
 </TabItem>
 <TabItem label="Manifest" value="Manifest-2">

calico_versioned_docs/version-3.26/getting-started/kubernetes/minikube.mdx

@@ -39,48 +39,48 @@ Enabling preinstalled $[prodname] might be the quickest way for testing. However
 :::
 
 ```bash
-minikube start --network-plugin=cni --cni=calico
+minikube start --cni=calico
 ```
 
 </TabItem>
 <TabItem label="Operator" value="Operator-1">
 
 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
+   ```
 
 </TabItem>
 <TabItem label="Manifest" value="Manifest-2">

calico_versioned_docs/version-3.27/getting-started/kubernetes/minikube.mdx

@@ -39,48 +39,48 @@ Enabling preinstalled $[prodname] might be the quickest way for testing. However
 :::
 
 ```bash
-minikube start --network-plugin=cni --cni=calico
+minikube start --cni=calico
 ```
 
 </TabItem>
 <TabItem label="Operator" value="Operator-1">
 
 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
+   ```
 
 </TabItem>
 <TabItem label="Manifest" value="Manifest-2">

calico_versioned_docs/version-3.28/getting-started/kubernetes/minikube.mdx

@@ -39,48 +39,48 @@ Enabling preinstalled $[prodname] might be the quickest way for testing. However
 :::
 
 ```bash
-minikube start --network-plugin=cni --cni=calico
+minikube start --cni=calico
 ```
 
 </TabItem>
 <TabItem label="Operator" value="Operator-1">
 
 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
+   ```
 
 </TabItem>
 <TabItem label="Manifest" value="Manifest-2">

calico_versioned_docs/version-3.29/getting-started/kubernetes/minikube.mdx

@@ -39,48 +39,48 @@ Enabling preinstalled $[prodname] might be the quickest way for testing. However
 :::
 
 ```bash
-minikube start --cni="calico"
+minikube start --cni=calico
 ```
 
 </TabItem>
 <TabItem label="Operator" value="Operator-1">
 
 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
+   ```
 
 </TabItem>
 <TabItem label="Manifest" value="Manifest-2">