Hi Ricky, Thanks for step by step instructions. All was good up until following calico install. But after issuing the command "kubectl create -f custom-resources.yaml", I get No resources found in calico-system namespace. Wonder if you can advise if possible. Many thanks. Kind regards,
Install the latest calico operator from the provided link docs.tigera.io/calico/latest/getting-started/kubernetes/self-managed-onprem/onpremises. Get used to checking the logs for kubelet, it will always give you an idea of what could be missing. You can do journalctl -xfeu kubelet on all nodes to see what kubelet is telling you.
@@rwahowa Thanks, but using the latest errors out saying already exists. How do I remove the previous version and try the latest? Would highly appreciate any help. Thanks.
@@sheetalgandhi2462 You can simply upgrade it: Upgrading an installation that uses the operator Download the v3.28 operator manifest: curl raw.githubusercontent.com/projectcalico/calico/v3.28.1/manifests/tigera-operator.yaml -O Use the following command to initiate an upgrade. kubectl apply --server-side --force-conflicts -f tigera-operator.yaml This is from the docs: docs.tigera.io/calico/latest/operations/upgrading/kubernetes-upgrade#upgrading-an-installation-that-uses-the-operator
I've just gone through the steps again on a new Virtualbox on Ubuntu, and the cluster was healthy. SO follow though the steps and check where you might have changed or missed something.
Hi Ricky, Thanks for step by step instructions. All was good up until following calico install. But after issuing the command "kubectl create -f custom-resources.yaml", I get No resources found in calico-system namespace. Wonder if you can advise if possible. Many thanks. Kind regards,
Install the latest calico operator from the provided link docs.tigera.io/calico/latest/getting-started/kubernetes/self-managed-onprem/onpremises. Get used to checking the logs for kubelet, it will always give you an idea of what could be missing. You can do journalctl -xfeu kubelet on all nodes to see what kubelet is telling you.
@@rwahowa Thanks, but using the latest errors out saying already exists. How do I remove the previous version and try the latest? Would highly appreciate any help. Thanks.
@@sheetalgandhi2462 You can simply upgrade it:
Upgrading an installation that uses the operator
Download the v3.28 operator manifest:
curl raw.githubusercontent.com/projectcalico/calico/v3.28.1/manifests/tigera-operator.yaml -O
Use the following command to initiate an upgrade.
kubectl apply --server-side --force-conflicts -f tigera-operator.yaml
This is from the docs:
docs.tigera.io/calico/latest/operations/upgrading/kubernetes-upgrade#upgrading-an-installation-that-uses-the-operator
Thanks, I will give it a try.
I've just gone through the steps again on a new Virtualbox on Ubuntu, and the cluster was healthy. SO follow though the steps and check where you might have changed or missed something.