Kubernetes Basics Training

In this guided hands-on training, we show the participants the basics of Kubernetes and select Kubernetes distributions.

Content Sections

The training content resides within the content directory.

The main part are the labs, which can be found at content/en/docs.

Hugo

This site is built using the static page generator Hugo.

The page uses the docsy theme which is included as a Hugo Module. Docsy is being enhanced using docsy-plus as well as docsy-acend and docsy-puzzle for brand specific settings.

The default configuration uses the acend setup from config/_default. Alternatively you can use the Puzzle setup from config/puzzle, which is enabled with --environment puzzle. Further, specialized environments exist, check out the config directory.

Docsy theme usage

• Official docsy documentation
• Docsy Plus

Update hugo module for theme updates

Run the following command to update all hugo modules with their newest upstream version:

hugo mod get -u

Command without hugo installation:

export HUGO_VERSION=$(grep "FROM docker.io/floryn90/hugo" Dockerfile | sed 's/FROM docker.io\/floryn90\/hugo://g' | sed 's/ AS builder//g')
docker run --rm --interactive -v $(pwd):/src docker.io/floryn90/hugo:${HUGO_VERSION} mod get -u

Build using Docker

Build the image:

docker build <--build-arg TRAINING_HUGO_ENV=...> -t acend/kubernetes-basics-training .

Run it locally:

docker run -i -p 8080:8080 acend/kubernetes-basics-training

Using Buildah and Podman

Build the image:

buildah build-using-dockerfile <--build-arg TRAINING_HUGO_ENV=...> -t acend/kubernetes-basics-training:latest .

Run it locally with the following command. Beware that --rmi automatically removes the built image when the container stops, so you either have to rebuild it or remove the parameter from the command.

podman run --rm --rmi --interactive --publish 8080:8080 localhost/acend/kubernetes-basics-training

How to develop locally

To develop locally we don't want to rebuild the entire container image every time something changed, and it is also important to use the same hugo versions like in production. We simply mount the working directory into a running container, where hugo is started in the server mode.

export HUGO_VERSION=$(grep "FROM docker.io/floryn90/hugo" Dockerfile | sed 's/FROM docker.io\/klakegg\/hugo://g' | sed 's/ AS builder//g')
docker run --rm --interactive --publish 8080:8080 -v $(pwd):/src docker.io/floryn90/hugo:${HUGO_VERSION} server -p 8080 --bind 0.0.0.0

use the following command to set the hugo environment

export HUGO_VERSION=$(grep "FROM docker.io/floryn90/hugo" Dockerfile | sed 's/FROM docker.io\/klakegg\/hugo://g' | sed 's/ AS builder//g')
docker run --rm --interactive --publish 8080:8080 -v $(pwd):/src docker.io/floryn90/hugo:${HUGO_VERSION} server --environment=<environment> -p 8080 --bind 0.0.0.0

Linting of Markdown content

Markdown files are linted with https://github.com/DavidAnson/markdownlint. Custom rules are in .markdownlint.json. There's a GitHub Action .github/workflows/markdownlint.yaml for CI. For local checks, you can either use Visual Studio Code with the corresponding extension, or the command line like this:

npm install
npm run mdlint

Npm not installed? no problem

export HUGO_VERSION=$(grep "FROM klakegg/hugo" Dockerfile | sed 's/FROM klakegg\/hugo://g' | sed 's/ AS builder//g')
docker run --rm --interactive -v $(pwd):/src klakegg/hugo:${HUGO_VERSION}-ci /bin/bash -c "set -euo pipefail;npm install; npm run mdlint;"

Github Actions

Build

The build action is fired on Pull Requests does the following

• builds all PR Versions (Linting and Docker build)
• deploys the built container images to the container registry
• Deploys a PR environment in a k8s test namespace with helm
• Triggers a redeployment
• Comments in the PR where the PR Environments can be found

PR Cleanup

The pr-cleanup action is fired when Pull Requests are closed and does the following

• Uninstalls PR Helm Release

Push Main

The push main action is fired when a commit is pushed to the main branch (eg. a PR is merged) and does the following, it's very similar to the Build Action

• builds main Versions (Linting and Docker build)
• deploys the built container images to the container registry
• Deploys the main Version on k8s using helm
• Triggers a redeployment

Helm

Manually deploy the training Release using the following command:

helm install --repo https://acend.github.io/helm-charts/  <release> acend-training-chart --values helm-chart/values.yaml -n <namespace>

For debugging purposes use the --dry-run parameter

helm install --dry-run --repo https://acend.github.io/helm-charts/  <release> acend-training-chart --values helm-chart/values.yaml -n <namespace>

Training parameters

Call the training site's URL and add the following parameters where appropriate in the form of:

<URL>/?<Parameter 1>=<Value 1>[&<Parameter n>=<Value n>]

e.g.:

<URL>/r=registry.example.com&a=appdomain.example.com

This will replace the placeholders with the values given.

Baloise

Parameter	Placeholder	Example
c	CHART-REPOSITORY-URL	charts.example.com
n	CLUSTER-NAME	osp1
r	REGISTRY-URL	registry.example.com

Contributions

If you find errors, bugs or missing information please help us improve and have a look at the Contribution Guide.