7
Oct, 2021
Installing Cilium via a ClusterResourceSet
CloudIn this post, I’m going to walk you through how to install Cilium onto a Cluster API-managed workload cluster using a ClusterResourceSet. It’s reasonable to consider this post a follow-up to my earlier post that walked you through using a ClusterResourceSet to install Calico. There’s no need to read the earlier post, though, as this post includes all the information (or links to the information) you need. Ready? Let’s jump in!
Prerequisites
If you aren’t already familiar with Cluster API—hereafter just referred to as CAPI—then I would encourage you to read my introduction to Cluster API post. Although it is a bit dated (it was written in the very early days of the project, which recently released version 1.0). Some of the commands referenced in that post have changed, but the underlying concepts remain valid. If you’re not familiar with Cilium, check out their introduction to the project for more information. Finally, if you’re not familiar at all with the idea of ClusterResourceSets, you can read my earlier post or check out the ClusterResourceSet CAEP document.
Installing Cilium via a ClusterResourceSet
If you want to install Cilium via a ClusterResourceSet, the process looks something like this:
- Create a ConfigMap with the instructions for installing Cilium.
- Create a ClusterResourceSet that references the ConfigMap.
- Profit (when you deploy matching workload clusters).
Let’s look at these steps in a bit more detail.
Creating the Installation ConfigMap
The Cilium docs generally recommend the use of the cilium CLI tool to install Cilium. The reasoning behind this is, as I understand it, that the cilium CLI tool can interrogate the Kubernetes cluster to gather information and then attempt to pick the best configuration options for you. Using helm is also another option recommended by the docs. For our purposes, however, neither of those approaches will work—using a ClusterResourceSet means you need to be able to supply YAML manifests.
Fortunately, the fact that Cilium supports Helm gives us a path forward via the use of helm template to render the templates locally. As per the docs on helm template, there are some caveats/considerations, but this was the only way I found to create YAML manifests for installing Cilium.
So, the first step to creating the ConfigMap you need is to set up the Helm repository:
helm repo add cilium https://helm.cilium.io
Then render the templates locally:
helm template cilium cilium/cilium --version 1.10.4 \
--namespace kube-system > cilium-1.10.4.yaml
You may need to specify additional options/values as needed in the above command in order to accommodate your specific environment or requirements, of course.
Once you have the templates rendered, then create the ConfigMap that the ClusterResourceSet needs:
kubectl create configmap cilium-crs-cm --from-file=cilium-1.10.4.yaml
This ConfigMap should be created on the appropriate CAPI management cluster, so ensure your Kubernetes context is set correctly.
Creating the ClusterResourceSet
Now you’re ready to create the ClusterResourceSet. Here’s an example you could use as a starting point:
---
apiVersion: addons.cluster.x-k8s.io/v1alpha4
kind: ClusterResourceSet
metadata: name: cilium-crs namespace: default
spec: clusterSelector: matchLabels: cni: cilium resources: - kind: ConfigMap name: cilium-crs-cm
You can see that the ClusterResourceSet references the ConfigMap, which in turn contains the YAML to install Cilium (and that’s the YAML applied against matching workload clusters).
Deploy a Matching Workload Cluster
What determines a matching workload cluster? The clusterSelector portion of the ClusterResourceSet. In the example above, the ClusterResourceSet’s clusterSelector specifies that workload clusters should have the cni: cilium label attached.
The label should be part of CAPI’s Cluster object, like this:
---
apiVersion: cluster.x-k8s.io/v1alpha4
kind: Cluster
metadata: name: cilium-cluster namespace: cilium-test labels: cni: cilium
When CAPI creates a workload cluster with that label and value, as shown in the example CAPI manifest above, then the ClusterResourceSet will automatically apply the contents of the ConfigMap against the cluster after it has been fully provisioned. The result: Cilium gets installed automatically on the new workload cluster!
I hope this post is useful. If you have any questions or any feedback, I’d love to hear from you! Feel free to find me on Twitter, or connect with me on the Kubernetes Slack instance. For more Cilium information and assistance, I’d encourage you to check out the Cilium Slack community.
…
6
Oct, 2021
VMWorld 2021 announced projects Summary
Cloud, VMware Cloud, VMworldVMworld 2021 is here, and as you would expect many big announcements are in the making. As it’s easy to get lost between Arctic, Ensemble, Capitola, Cascade, Monterey, Radium projects announcements, so here is small summary about each one. It can help as well in case you missed one of them or looking for more details:-
Project Arctic:-
Project Arctic will bring multi-cloud to the fingertips of vSphere customers, by natively integrating cloud connectivity into vSphere – making vSphere cloud-aware, and making hybrid cloud the “default” operating model. Millions of IT Admins who use vCenter on-premises will be able to leverage their domain expertise and benefit from expanded cloud capabilities. Customers would be able to instantly access VMware Cloud capacity and deploy VMware Cross-Cloud Services – for example, they would be able to enable disaster recovery to the cloud with just a few clicks, or leverage security services for threat detection and ransomware protection.
Project Cascade:-
Project Cascade will provide a unified Kubernetes interface for both on-demand infrastructure (IaaS) and containers (CaaS) across VMware Cloud – available through an open command line interface (CLI), APIs, or a GUI dashboard. Project Cascade will address the needs of developers and DevOps in a multi-cloud world.… Read More
…