arlonproj / arlon

A kubernetes cluster lifecycle management and configuration tool
Apache License 2.0
146 stars 14 forks source link

decide what to do with CNI, and also should clusters have more than one profile? #22

Open bcle opened 2 years ago

bcle commented 2 years ago

Now that arlon supports CAPI-AWS-kubeadm clusters, the issue of CNI came up. A CAPI kubeadm cluster starts with no CNI, so any bundles that install workloads (e.g. applications) will be stuck in the progressing state. This was a great opportunity for me to define a CNI setup as a bundle (I created a static bundle from a file downloaded from https://docs.projectcalico.org/v3.21/manifests/calico.yaml), and then add the bundle to the cluster's dynamic profile. As expected, the cluster was automatically updated with calico, and the workloads eventually deployed successfully. However, if CAPI EKS clusters were using the same dynamic profile, they would potentially break, since they are automatically configured with AWS VPC CNI out of the box, resulting in a conflict. So this raises important questions about how to treat CNIs. Possible approaches:

Aha! Link: https://pf9.aha.io/features/ARLON-169

cre8minus1 commented 2 years ago

@bcle what was the verdict on CNI? and should the Multiple Profile issue be split out