CKAD Scenarios about CRDs and Helm
Custom Resource Definitions and Helm were added to the recent CKAD exam update, let’s learn those!
FREE CKAD Scenarios? YES!
(we also already have CKA and CKS ones)
killercoda.com/killer-shell-ckad
This weeks scenarios
The CKAD has been updated recently and added new topics, among these two for which we added scenarios this week:
Custom Resource Definitions
Custom Resource Definitions allow everyone to extend Kubernetes. There are various default K8s resources, famous ones are a Pod or a Deployment. There are a bunch of baked-in resources like this, always depending on your K8s version.
With CRDs it’s possible to create own resources, for example one named Abc. Everyone wanting to use your resource would just need to install your CRD definition and maybe controllers that can work with it.
If CRDs did exist in the very beginning of K8s, then all existing resources like Pods would probably be defined as a CRD.
For the CKAD it’s important to Discover and use resources that extend Kubernetes (CRD), and this is what we do in this scenario.
Helm Package Manager
Helm Chart: Kubernetes YAML template-files combined into a single package, Values allow customisation
Helm Release: Installed instance of a Chart
Helm Values: Allow to customise the YAML template-files in a Chart when creating a ReleaseHelm Registry: Collection of Helm Charts
If you work with K8s clusters and find yourself wanting to install something, like Grafana, most of the time the easiest way is to just use Helm. Helm is a package manager for K8s which allows to install Helm Charts from various Helm Registries.
For the CKAD it’s important to be able to Use the Helm package manager to deploy existing packages, and this it what we do in this scenario.
What’s next?
We plan to create new CKAD challenges weekly and post here about it. Any topics you would like to see next? Let us know in the comments!
