Calico

https://docs.tigera.io/calico/latest/
Admin
Calico is a unified platform for Kubernetes networking, network security, and observability that...
Tokens:272,963
Snippets:2,461
Trust Score:10
Update:1 week ago
Show doc for...
Tokens:
Raw
### Start minikube with network plugin for Manifest installation

Source: https://docs.tigera.io/calico/latest/getting-started/kubernetes/minikube

Starts a minikube cluster with one control plane node using the --network-plugin=cni flag for the Manifest installation method.

```bash
minikube start --network-plugin=cni
```

--------------------------------

### Example output of kubectl get nodes

Source: https://docs.tigera.io/calico/latest/getting-started/kubernetes/self-managed-public-cloud/gce

Example output showing nodes in NotReady status before Calico is installed.

```text
NAME         STATUS     ROLES    AGE     VERSION  

controller   NotReady   master   5m49s   v1.17.2  

worker-0     NotReady   <none>   3m38s   v1.17.2  

worker-1     NotReady   <none>   3m7s    v1.17.2  

worker-2     NotReady   <none>   5s      v1.17.2  
```

--------------------------------

### Run BusyBox pod for testing

Source: https://docs.tigera.io/calico/latest/getting-started/kubernetes/quickstart

Starts a BusyBox pod in the 'quickstart' namespace and opens a shell session inside it. The pod is removed when the session exits.

```bash
kubectl run --namespace=quickstart access --rm -ti --image busybox /bin/sh  
```

```text
If you don't see a command prompt, try pressing enter.  

/ #  
```

--------------------------------

### Example output of kubectl get nodes

Source: https://docs.tigera.io/calico/latest/getting-started/kubernetes/managed-public-cloud/eks

Example output from 'kubectl get nodes -o wide' showing a node with Ready status.

```text
NAME              STATUS   ROLES    AGE   VERSION   INTERNAL-IP   EXTERNAL-IP   OS-IMAGE             KERNEL-VERSION    CONTAINER-RUNTIME  

<your-hostname>   Ready    master   52m   v1.12.2   10.128.0.28   <none>        Ubuntu 18.04.1 LTS   4.15.0-1023-gcp   docker://18.6.1  
```

--------------------------------

### Example output of kubectl get nodes

Source: https://docs.tigera.io/calico/latest/getting-started/kubernetes/nftables

Example output from `kubectl get nodes -o wide` showing a single ready node.

```text
NAME              STATUS   ROLES    AGE   VERSION   INTERNAL-IP   EXTERNAL-IP   OS-IMAGE             KERNEL-VERSION    CONTAINER-RUNTIME  

<your-hostname>   Ready    master   52m   v1.12.2   10.128.0.28   <none>        Ubuntu 18.04.1 LTS   4.15.0-1023-gcp   docker://18.6.1  


```

--------------------------------

### Install and start Nova Metadata API on non-controller nodes

Source: https://docs.tigera.io/calico/latest/getting-started/openstack/installation/redhat

Install and start the Nova Metadata API on compute nodes that are not controllers. Not required on combined compute and controller nodes.

```bash
yum install -y openstack-nova-api  

service openstack-nova-metadata-api restart  

chkconfig openstack-nova-metadata-api on  
```

--------------------------------

### Create quickstart namespace

Source: https://docs.tigera.io/calico/latest/getting-started/kubernetes/quickstart

Creates a namespace named 'quickstart' for the NGINX and BusyBox deployment.

```bash
kubectl create namespace quickstart  
```

```text
namespace/quickstart created  
```

--------------------------------

### Create OpenShift cluster with openshift-install

Source: https://docs.tigera.io/calico/latest/getting-started/kubernetes/openshift/installation

Starts the cluster creation process. Wait for the command to complete before verifying Calico installation.

```bash
openshift-install create cluster  

```

--------------------------------

### Install kubeadm, kubelet, and kubectl on each node

Source: https://docs.tigera.io/calico/latest/getting-started/kubernetes/self-managed-public-cloud/gce

Run these commands on each worker and controller node to install Kubernetes tools. Adds the Kubernetes apt repository and installs kubelet, kubeadm, and kubectl, then holds their versions.

```bash
curl -fsSL https://dl.k8s.io/apt/doc/apt-key.gpg | sudo apt-key add -  

cat <<EOF | sudo tee /etc/apt/sources.list.d/kubernetes.list  

deb https://pkgs.k8s.io/ kubernetes-xenial main  

EOF  

sudo apt-get update  

sudo apt-get install -y kubelet kubeadm kubectl  

sudo apt-mark hold kubelet kubeadm kubectl  
```

--------------------------------

### Example kubeadm join command for Windows node

Source: https://docs.tigera.io/calico/latest/getting-started/kubernetes/windows-calico/operator

Example join command with the kubeadm.exe path updated to c:\k\kubeadm.exe and the --cri-socket flag appended for Kubernetes versions earlier than v1.25. Run this on the Windows node; the node will appear as NotReady until the Calico CNI is installed.

```bash
c:\k\kubeadm.exe join 172.16.101.139:6443 --token v8w2jt.jmc45acn85dbll1e --discovery-token-ca-cert-hash sha256:d0b7040a704d8deb805ba1f29f56bbc7cea8af6aafa78137a9338a62831739b4 --cri-socket "npipe:////./pipe/containerd-containerd"
```

--------------------------------

### Example output of Get-BgpCustomRoute

Source: https://docs.tigera.io/calico/latest/getting-started/kubernetes/windows-calico/troubleshoot

Example output showing the routes exported by the host.

```text
10.243.214.152/29  
10.243.214.160/29  
10.243.214.168/29  
10.244.42.0/26  
```

--------------------------------

### Install Calico using manifest

Source: https://docs.tigera.io/calico/latest/getting-started/kubernetes/minikube

Installs Calico by applying the calico.yaml manifest.

```bash
kubectl apply -f https://raw.githubusercontent.com/projectcalico/calico/v3.33.0/manifests/calico.yaml
```

--------------------------------

### Install openstack-neutron package

Source: https://docs.tigera.io/calico/latest/getting-started/openstack/installation/redhat

Install Neutron infrastructure code on the compute host.

```bash
yum install -y openstack-neutron  
```

--------------------------------

### Install Docker on each VM

Source: https://docs.tigera.io/calico/latest/getting-started/kubernetes/self-managed-public-cloud/gce

Installs Docker and required packages on the controller and worker VMs.

```bash
sudo apt update
sudo apt install -y docker.io
sudo systemctl enable docker.service
sudo apt install -y apt-transport-https curl  
```

--------------------------------

### Expected output of kubectl get nodes -o wide

Source: https://docs.tigera.io/calico/latest/getting-started/kubernetes/kind

Example output from 'kubectl get nodes -o wide' showing the three nodes with NotReady status, as expected before Calico is installed.

```text
NAME                STATUS      ROLES           AGE    VERSION   INTERNAL-IP   EXTERNAL-IP   OS-IMAGE             KERNEL-VERSION    CONTAINER-RUNTIME  

dev-control-plane   NotReady    control-plane   4m     v1.25.0   172.18.0.2    <none>        Ubuntu 22.04.1 LTS   5.10.0-17-amd64   containerd://1.6.7  

dev-worker          NotReady    <none>          4m     v1.25.0   172.18.0.4    <none>        Ubuntu 22.04.1 LTS   5.10.0-17-amd64   containerd://1.6.7  

dev-worker2         NotReady    <none>          4m     v1.25.0   172.18.0.3    <none>        Ubuntu 22.04.1 LTS   5.10.0-17-amd64   containerd://1.6.7  

```

--------------------------------

### Create frontend, backend, client, and management-ui apps

Source: https://docs.tigera.io/calico/latest/network-policy/get-started/kubernetes-policy/kubernetes-demo

Run these kubectl commands to create the namespaces and services for the demo. Wait for all pods to enter Running state before proceeding.

```bash
kubectl create -f https://docs.tigera.io/files/00-namespace.yaml  

kubectl create -f https://docs.tigera.io/files/01-management-ui.yaml  

kubectl create -f https://docs.tigera.io/files/02-backend.yaml  

kubectl create -f https://docs.tigera.io/files/03-frontend.yaml  

kubectl create -f https://docs.tigera.io/files/04-client.yaml  

```

--------------------------------

### Install Calico using the manifest method

Source: https://docs.tigera.io/calico/latest/getting-started/kubernetes/k3s/quickstart

Run this command to install Calico using the manifest method. The output shows the resources created.

```bash
kubectl apply -f https://raw.githubusercontent.com/projectcalico/calico/v3.33.0/manifests/calico.yaml
```

```bash
configmap/calico-config created

customresourcedefinition.apiextensions.k8s.io/bgpconfigurations.crd.projectcalico.org created

customresourcedefinition.apiextensions.k8s.io/bgppeers.crd.projectcalico.org created

customresourcedefinition.apiextensions.k8s.io/blockaffinities.crd.projectcalico.org created

customresourcedefinition.apiextensions.k8s.io/clusterinformations.crd.projectcalico.org created

customresourcedefinition.apiextensions.k8s.io/felixconfigurations.crd.projectcalico.org created

customresourcedefinition.apiextensions.k8s.io/globalnetworkpolicies.crd.projectcalico.org created

customresourcedefinition.apiextensions.k8s.io/globalnetworksets.crd.projectcalico.org created

customresourcedefinition.apiextensions.k8s.io/hostendpoints.crd.projectcalico.org created

customresourcedefinition.apiextensions.k8s.io/ipamblocks.crd.projectcalico.org created

customresourcedefinition.apiextensions.k8s.io/ipamconfigs.crd.projectcalico.org created

customresourcedefinition.apiextensions.k8s.io/ipamhandles.crd.projectcalico.org created

customresourcedefinition.apiextensions.k8s.io/ippools.crd.projectcalico.org created

customresourcedefinition.apiextensions.k8s.io/kubecontrollersconfigurations.crd.projectcalico.org created

customresourcedefinition.apiextensions.k8s.io/networkpolicies.crd.projectcalico.org created

customresourcedefinition.apiextensions.k8s.io/networksets.crd.projectcalico.org created

clusterrole.rbac.authorization.k8s.io/calico-kube-controllers created

clusterrolebinding.rbac.authorization.k8s.io/calico-kube-controllers created

clusterrole.rbac.authorization.k8s.io/calico-node created

clusterrolebinding.rbac.authorization.k8s.io/calico-node created

daemonset.apps/calico-node created

serviceaccount/calico-node created

deployment.apps/calico-kube-controllers created

serviceaccount/calico-kube-controllers created
```

--------------------------------

### Verify application pods are ready

Source: https://docs.tigera.io/calico/latest/network-policy/istio/enforce-policy-istio

Lists all pods to verify that the demo application has come up. Expected output shows three pods running.

```bash
kubectl get pods  
```

```text
NAME                        READY     STATUS    RESTARTS   AGE  
customer-2809159614-qqfnx   3/3       Running   0          21h  
database-1601951801-m4w70   3/3       Running   0          21h  
summary-2817688950-g1b3n    3/3       Running   0          21h  
```

--------------------------------

### Example output of kubectl get pods

Source: https://docs.tigera.io/calico/latest/getting-started/kubernetes/managed-public-cloud/gke

Example output from the kubectl get pods command, showing the Calico pods and other system pods running in the kube-system namespace.

```text
NAME                                                           READY   STATUS    RESTARTS   AGE  
calico-node-hjnt5                                              1/1     Running   0          13m  
calico-node-phcjw                                              1/1     Running   0          13m  
calico-node-pmrkm                                              1/1     Running   0          12m  
calico-node-vertical-autoscaler-8c79c8dc-q7z7c                 1/1     Running   0          15m  
calico-typha-547bf5ddbd-8jlnt                                  1/1     Running   0          13m  
calico-typha-547bf5ddbd-d2qjd                                  1/1     Running   0          13m  
calico-typha-horizontal-autoscaler-7d99b54d8b-f9fq6            1/1     Running   0          15m  
calico-typha-vertical-autoscaler-bbdb9bc58-wsd6v               1/1     Running   0          15m  
event-exporter-gke-545bc64577-rmgkn                            2/2     Running   0          15m  
fluentbit-gke-8p8tc                                            3/3     Running   0          14m  
...  
```

--------------------------------

### Verify Calico installation with kubectl get pods -A

Source: https://docs.tigera.io/calico/latest/getting-started/kubernetes/k3s/multi-node-install

Output of `kubectl get pods -A` after installing Calico on a multi-node K3s cluster. The first block shows the operator-based installation with pods in the tigera-operator and calico-system namespaces; the second shows the manifest-based installation with pods in the kube-system namespace. All pods are Running.

```text
NAMESPACE         NAME                                      READY   STATUS    RESTARTS   AGE  

tigera-operator   tigera-operator-c9cf5b94d-gj9qp           1/1     Running   0          107s  

calico-system     calico-typha-7dcd87597-npqsf              1/1     Running   0          88s  

calico-system     calico-node-rdwwz                         1/1     Running   0          88s  

kube-system       local-path-provisioner-6d59f47c7-4q8l2    1/1     Running   0          2m14s  

kube-system       metrics-server-7566d596c8-xf66d           1/1     Running   0          2m14s  

kube-system       coredns-8655855d6-wfdbm                   1/1     Running   0          2m14s  

calico-system     calico-kube-controllers-89df8c6f8-7hxc5   1/1     Running   0          87s  

```

```text
NAMESPACE     NAME                                       READY   STATUS    RESTARTS   AGE  

kube-system   calico-node-9hn9z                    1/1     Running   0          23m  

kube-system   local-path-provisioner-6d59f47c7-drznc     1/1     Running   0          38m  

kube-system   calico-kube-controllers-789f6df884-928lt   1/1     Running   0          23m  

kube-system   metrics-server-7566d596c8-qxlfz            1/1     Running   0          38m  

kube-system   coredns-8655855d6-blzl5                    1/1     Running   0          38m  

```

--------------------------------

### Example kubeadm join command from init output

Source: https://docs.tigera.io/calico/latest/getting-started/kubernetes/self-managed-public-cloud/gce

Example of the join command output by kubeadm init. Use this command on worker nodes to join them to the cluster.

```bash
kubeadm join 10.240.0.11:6443 --token ar77y2.7274jxuumt8vhhvw \

  --discovery-token-ca-cert-hash sha256:d913182b646660c7be5bd76c1b9e9fa3e613ed9c18ef36ad0d475f8f7c887331   
```

--------------------------------

### Boot a VM on the tenant network

Source: https://docs.tigera.io/calico/latest/networking/openstack/floating-ips

Boots a VM on the tenant network. The command is shown as a placeholder with '[...]' for additional options.

```bash
nova boot [...]  

```

--------------------------------

### Start RemoteAccess service

Source: https://docs.tigera.io/calico/latest/getting-started/kubernetes/windows-calico/operator

Ensure the RemoteAccess service is running, as it may fail to start automatically after installation.

```powershell
Start-Service RemoteAccess  
```

--------------------------------

### Output of calicoctl get nodes

Source: https://docs.tigera.io/calico/latest/network-policy/comms/secure-metrics

Example output of the calicoctl get nodes command, showing two nodes in the cluster.

```text
NAME  

kubeadm-master  

kubeadm-node-0  

```

--------------------------------

### Install Calico by creating custom resources

Source: https://docs.tigera.io/calico/latest/getting-started/kubernetes/k3s/quickstart

Run this command to install Calico by creating the necessary custom resource. Before running, read the manifest and adjust settings such as the default IP pool CIDR to match your pod network CIDR.

```bash
kubectl create -f https://raw.githubusercontent.com/projectcalico/calico/v3.33.0/manifests/custom-resources.yaml
```

--------------------------------

### Prepare Windows node for kubeadm join

Source: https://docs.tigera.io/calico/latest/getting-started/kubernetes/windows-calico/operator

Downloads and runs the PrepareNode.ps1 script to install kubeadm and kubelet binaries and set up the kubelet service. Specify the Kubernetes version, e.g., v1.26.6.

```powershell
Invoke-WebRequest https://raw.githubusercontent.com/kubernetes-sigs/sig-windows-tools/master/hostprocess/PrepareNode.ps1 -OutFile c:\PrepareNode.ps1

c:\PrepareNode.ps1 -KubernetesVersion v1.26.6
```

--------------------------------

### Output of calicoctl get nodes

Source: https://docs.tigera.io/calico/latest/network-policy/comms/secure-metrics

Example output from the `calicoctl get nodes` command, showing two nodes named `kubeadm-master` and `kubeadm-node-0`.

```text
NAME  
kubeadm-master  
kubeadm-node-0  
```

--------------------------------

### Expected output of kubectl get nodes

Source: https://docs.tigera.io/calico/latest/networking/ingress-gateway/tutorial-ingress-gateway-canary

Expected output from kubectl get nodes, showing three nodes with NotReady status until Calico networking is installed.

```text
NAME                           STATUS     ROLES           AGE     VERSION  

calico-cluster-control-plane   NotReady   control-plane   5m46s   v1.33.1  

calico-cluster-worker          NotReady   <none>          5m23s   v1.33.1  

calico-cluster-worker2         NotReady   <none>          5m22s   v1.33.1  
```

--------------------------------

### Initialize MicroK8s node with snap install

Source: https://docs.tigera.io/calico/latest/getting-started/kubernetes/microk8s

Installs MicroK8s as a classic snap package. Requires a Linux host with snapd support and at least 4GB RAM and 20GB free disk space.

```bash
snap install microk8s --classic
```

--------------------------------

### Example output of kubectl get endpoints kubernetes

Source: https://docs.tigera.io/calico/latest/getting-started/kubernetes/windows-calico/operator

Shows the expected output with a single IP and port under ENDPOINTS.

```text
NAME         ENDPOINTS             AGE  

kubernetes   172.16.101.157:6443   40m  
```

--------------------------------

### Create router and connect tenant and external networks

Source: https://docs.tigera.io/calico/latest/networking/openstack/floating-ips

Creates a router named 'router1', adds the tenant subnet as an interface, and sets the external network as the gateway.

```bash
neutron router-create router1  

neutron router-interface-add router1 <tenant-subnet-id>  

neutron router-gateway-set router1 public  

```

--------------------------------

### Example output of custom host endpoints

Source: https://docs.tigera.io/calico/latest/network-policy/hosts/kubernetes-nodes

Sample output showing host endpoints created from custom templates.

```text
NAME                                                            NODE                              INTERFACE   IPS               PROFILES

192.168.83.64.compute.internal-custom-host-endpoint-auto-hep    192.168.83.64.compute.internal                192.168.83.64     projectcalico-default-allow

192.168.0.128.compute.internal-custom-host-endpoint-auto-hep    192.168.0.128.compute.internal                192.168.0.128     projectcalico-default-allow

192.168.157.128.compute.internal-custom-host-endpoint-auto-hep  192.168.157.128.compute.internal              192.168.157.128   projectcalico-default-allow
```

--------------------------------

### Verify IP pools with kubectl get ippools

Source: https://docs.tigera.io/calico/latest/networking/ipam/ippools

After installing Calico, use this command to confirm the IP pools were created.

```bash
kubectl get ippools  


```

--------------------------------

### Expected pod status output (initial)

Source: https://docs.tigera.io/calico/latest/getting-started/kubernetes/windows-calico/demo

Example output showing busybox and nginx running, while porter and pwsh are ContainerCreating. This is the expected initial state after applying the manifest.

```text
NAME      READY   STATUS              RESTARTS   AGE  

busybox   1/1     Running             0          4m14s  

nginx     1/1     Running             0          4m14s  

porter    0/1     ContainerCreating   0          74s  

pwsh      0/1     ContainerCreating   0          2m9s  
```

--------------------------------

### Get AKS cluster credentials

Source: https://docs.tigera.io/calico/latest/getting-started/kubernetes/managed-public-cloud/aks

Retrieves credentials to access the AKS cluster with kubectl. Run after creating the cluster and before installing Calico.

```bash
az aks get-credentials --resource-group my-calico-rg --name my-calico-cluster  
```

--------------------------------

### Example output of kubecontrollersconfiguration

Source: https://docs.tigera.io/calico/latest/network-policy/hosts/kubernetes-nodes

Sample output showing the updated KubeControllersConfiguration with custom templates.

```yaml
apiVersion: projectcalico.org/v3
kind: KubeControllersConfiguration
metadata:
  name: default
spec:
  controllers:
    node:
      hostEndpoint:
        autoCreate: Enabled
        createDefaultHostEndpoint: Enabled
        templates:
        - generateName: custom-host-endpoint
          interfaceCIDRs:
          - 192.168.0.0/16
          labels:
            custom-label: template-host-endpoint
          annotations:
            custom-annotation: template-host-endpoint
```

--------------------------------

### Operator Installation for IPv6 only

Source: https://docs.tigera.io/calico/latest/networking/ipam/ipv6

Example Installation resource for the Calico operator to configure an IPv6-only cluster. It defines a single IPv6 IP pool with no IPv4 pools. Requires Calico IPAM and a Kubernetes cluster with IPv6 pod CIDR and service IP range.

```yaml
apiVersion: operator.tigera.io/v1  

kind: Installation  

metadata:  

  name: default  

spec:  

  calicoNetwork:  

    ipPools:  

      - blockSize: 122  

        cidr: 2001::00/64  

        encapsulation: None  

        natOutgoing: Enabled  

        nodeSelector: all()  

```

--------------------------------

### Example output of host endpoints

Source: https://docs.tigera.io/calico/latest/network-policy/hosts/kubernetes-nodes

Sample output showing automatically created host endpoints.

```text
NAME                                                    NODE                                           INTERFACE   IPS                              PROFILES

ip-172-16-101-147.us-west-2.compute.internal-auto-hep   ip-172-16-101-147.us-west-2.compute.internal   *           172.16.101.147,192.168.228.128   projectcalico-default-allow

ip-172-16-101-54.us-west-2.compute.internal-auto-hep    ip-172-16-101-54.us-west-2.compute.internal    *           172.16.101.54,192.168.107.128    projectcalico-default-allow

ip-172-16-101-79.us-west-2.compute.internal-auto-hep    ip-172-16-101-79.us-west-2.compute.internal    *           172.16.101.79,192.168.91.64      projectcalico-default-allow

ip-172-16-101-9.us-west-2.compute.internal-auto-hep     ip-172-16-101-9.us-west-2.compute.internal     *           172.16.101.9,192.168.71.192      projectcalico-default-allow

ip-172-16-102-63.us-west-2.compute.internal-auto-hep    ip-172-16-102-63.us-west-2.compute.internal    *           172.16.102.63,192.168.108.192    projectcalico-default-allow
```

--------------------------------

### Start minikube with custom pod network CIDR for Operator installation

Source: https://docs.tigera.io/calico/latest/getting-started/kubernetes/minikube

Starts a minikube cluster with one control plane node, disabling the default CNI and configuring a pod network CIDR of 192.168.0.0/16. If this CIDR is already in use in your network, replace it with a different one.

```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
```

--------------------------------

### Deploy NGINX deployment

Source: https://docs.tigera.io/calico/latest/getting-started/kubernetes/quickstart

Deploys an NGINX web server in the 'quickstart' namespace.

```bash
kubectl create deployment --namespace=quickstart nginx --image=nginx  
```

```text
deployment.apps/nginx created  
```

--------------------------------

### Sample EnvironmentFile for etcdv3 datastore

Source: https://docs.tigera.io/calico/latest/getting-started/bare-metal/installation/binary-mgr

Sample environment file to save to /etc/calico/calico.env. Sets etcdv3 datastore connection variables.

```bash
FELIX_DATASTORETYPE=etcdv3  

FELIX_ETCDENDPOINTS=https://calico-datastore.example.com:2379  

FELIX_ETCDCAFILE="/pki/ca.pem"  

FELIX_ETCDCERTFILE="/pki/client-cert.pem"  

FELIX_ETCDKEYFILE="/pki/client-key.pem"  

```

--------------------------------

### Create Calico custom resources

Source: https://docs.tigera.io/calico/latest/getting-started/kubernetes/kind

Install Calico by creating the necessary custom resource. Read the manifest contents first and adjust settings like pod-network-cidr for your environment.

```bash
kubectl create -f https://raw.githubusercontent.com/projectcalico/calico/v3.33.0/manifests/custom-resources.yaml  

```

--------------------------------

### Expected output from Calico verification

Source: https://docs.tigera.io/calico/latest/getting-started/kubernetes/kind

Example output from the verification command, showing calico-node pods running. Namespace may differ depending on installation method.

```text
NAMESPACE     NAME                READY   STATUS    RESTARTS   AGE  
kube-system   calico-node-2xcf4   1/1     Running   0          57s  
kube-system   calico-node-gkqkg   1/1     Running   0          57s  
kube-system   calico-node-j44hp   1/1     Running   0          57s  

```

--------------------------------

### Get RHEL Entitlement data for OpenShift WireGuard installation

Source: https://docs.tigera.io/calico/latest/network-policy/encrypt-cluster-pod-traffic

Command to create a tarball of RHEL entitlement data and subscription manager files from a RHEL8 host in the cluster.

```bash
tar -czf subs.tar.gz /etc/pki/entitlement/ /etc/rhsm/ /etc/yum.repos.d/redhat.repo  

```

--------------------------------

### Default IPPool Output from calicoctl get ippool -o wide

Source: https://docs.tigera.io/calico/latest/networking/ipam/assign-ip-addresses-topology

Shows the output of `calicoctl get ippool -o wide` after installing Calico without setting a matching default IP pool. It indicates Calico created the default IP pool `192.168.0.0/16` with selector all(). This output is used before deleting the default pool.

```text
NAME                  CIDR             NAT    IPIPMODE   DISABLED   SELECTOR  

default-ipv4-ippool   192.168.0.0/16   true   Always     false      all()  

```

--------------------------------

### Expected output for successful busybox to porter connection

Source: https://docs.tigera.io/calico/latest/getting-started/kubernetes/windows-calico/demo

If the connection from the busybox pod to the porter pod succeeds, you will get output similar to this. The IP addresses will vary depending on your environment setup.

```text
192.168.40.166 (192.168.40.166:80) open
```

--------------------------------

### Start minikube with built-in Calico

Source: https://docs.tigera.io/calico/latest/getting-started/kubernetes/minikube

Starts a minikube cluster with Calico preinstalled using the --cni=calico flag. This is the quickest way to test Calico features, but may not include the most recent version or features.

```bash
minikube start --cni=calico
```
Tokens:
Raw