This repository contains the exercises used in the kubernetes course. It has a folder for each exercise and the solution is available in a separate directory.
The exercises can be performed in 2 different environments:
The recommendation for this course is to use a real kubernetes cluster, as this is the most realistic situation. However, most exercises can be performed on both, only the services/persistent volumes/ingress exercises are different. When there are separate instructions for both situation.
Usage:
- run the following command in gitpod to get access to the cluster:
gp idp login aws --role-arn arn:aws:iam::299641483789:role/kubernetes-workshop-gitpod-role --duration-seconds=28800 - run then:
./connect_cluster.sh k8s-24vTxK
More details on how to integrate gitpod with an eks cluster can be found on the following link: https://www.gitpod.io/docs/integrations/aws
- Create a namespace for yourself and make sure to create all resources in your own namespace such that you do not impact each other. The kubens command ensures that your kube context is set to your namespaces instead of the default one.
kubectl create namespace <your-first-name>
kubens <select your namespace>
If you do not have a kubernetes cluster to run against, I can recommend microk8s to simulate a k8s cluster on your local machine. More info on installing microk8s can be found at: https://microk8s.io/docs/getting-started
- Exercise 1: using pod spec
- Exercise 2: kubernetes commands
- Exercise 3: livecycle pods
- Exercise 4: deployments
- Exercise 5: secrets
- Exercise 6: configmaps
- Exercise 7: services
- Exercise 8: ingress
- Exercise 9: persistent volumes
- Exercise 10: stateful sets
- Exercise 11: init containers
- Exercise 12: daemonsets
- Exercise 13: rbac
- Exercise 14: Kustomize basic
- Exercise 15: Kustomize with generated configmap and secret
- Exercise 16: Using a helm chart
- Exercise 17: Creating a helm chart