ralgozino
commented
2 years ago Left some comments.
What is our mid/long-term plan for this module? Do we want to fully move to Tigera? What are the upstream project's recommendations about that?
The main idea behind introducing the operator is to provide the policy-only mode for EKS clusters, so we are not missing any pieces there. The on-prem deployment for the operator was "for free", I had to do it anyway for the policy-only mode.
Even though upstream still maintains the manifests installations they are pushing the Operator-based installation, and even say that the manifests installation is "not recommended", so we'll have to eventually migrate to the operator IMO.
Calico can also be installed using raw manifests as an alternative to the operator. The manifests contain the necessary resources for installing Calico on each node in your Kubernetes cluster. Using manifests is not recommended as they cannot automatically manage the lifecycle of the Calico as the operator does. However, manifests may be useful for clusters that require highly specific modifications to the underlying Kubernetes resources. From: https://projectcalico.docs.tigera.io/getting-started/kubernetes/self-managed-onprem/onpremises
I'd like to introduce the operator in this release and after some testing start migrating over (unless we find any blockers), this is the reason why I also did not update the main readme changing the instructions to the operator.
Introduce the Tigera Operator to the Networking module. Including:
Tested:
Fixes #38 Fixes #39