Evolution of application deployment over the past 20 years.
Configure your local and remote lab environments.
Covers the resource types that are included with Kubernetes.
•Pod
•Job
Using helm to manage Kubernetes resources
Example microservice application.
Kubernetes manifests to deploy the demo application.
Explore how custom resources can add functionality
Install additional software to enhance the deployment.
Improving the DevX when working with Kubernetes.
How to safely upgrade your clusters and nodes.
Implement CI/CD for your applications (with GitOps!)
Helm is both a package manager and templating engine for Kubernetes. It bundles related manifests and configuration into charts that can be stored in a Helm repository or an OCI registry. When you install a chart, Helm renders the templates with your chosen values and creates a release in the cluster.
A chart typically contains:
Chart.yaml
for metadatavalues.yaml
with default configurationtemplates/
directory holding Kubernetes manifestsTemplates can reference chart and release metadata, define variables, include conditionals, and loop over values. For example:
apiVersion: v1
kind: Pod
metadata:
name: example
spec:
containers:
- image: nginx:{{ .Values.version }}
Real-world charts often become quite complex as they accommodate many deployment scenarios. Thankfully the helm
CLI provides commands such as helm install
, helm upgrade
, and helm rollback
to manage releases.
We'll spend the rest of this module getting hands-on with Helm—consuming existing charts and eventually writing a simple chart of our own.