Creating a Custom Competitive Kubernetes Training Experience on AKS — Part 2


In the last section we’ve made some initial design decisions which will influence our solution.

In this section we’ll pick a database, review and insert some questions, review the apis and a sample sequence flow, review our overall architecture and finally deploy our kubernetes applications.


We are going to simply pick Sqlite for our relational database needs, due it’s small nature and ease of use and it’s file based nature. We’ll mount the Sqlite database onto a PVC (Azure Disk) to maintain state.

Question and Levels

New Level

Inserting a new level is straight forward

New Question — Hands on

This question type may setup some k8s resources inside your namespace and then ask you to perform some additional tasks. In the below example we create a random deployment into your namespace and you are then required to create a kubernetes docker secret called regcred. The validation will then be performed by executing the answer_query against the namespace and comparing the output to the answer_value. See Question 1 in the Demo on Part 1

New Question — Hands on Multiple Choice

Like the previous question, this one also sets up some kubernetes resources in your namespace but doesn’t require you to perform any deployments to your namespace. Instead you are required to do some investigative work inside the namespace and then pick a multiple choice answer.

In the example below, we deploy a secret and ask you to identify the name of this secret giving you 3 possible answers. See Question 3 in the Demo on Part 1

New Question — Multiple Choice

This question type doesn’t require the user to sign in to their namespace, instead it is just a simple multiple choice question. See Question 2 in the Demo on Part 1


At a high level we’ll need to create the following simple api’s.

High Level Sequence Diagram of “Hands on” Question Type

AKS Architecture

Azure Resources

In the above Architecture, we’ll setup Azure Resources from our previous medium article:

This includes our AKS cluster, load balancer, private DNS, our windows VM etc

Kubernetes Resources

As we are using a private domain name (hynes.pri) which does not exist outside our Azure Subscription, we will generate a Self Signed Cert for both kompui.hynes.pri and kompservice.hynes.pri and create kubernetes tls secrets from the resulting key and cert.

UI Application Source Code (Including Dockerfile and K8s Manifests)

Server Application Source Code (Including Dockerfile and K8s Manifests)


I hope you have found this set of articles and source code useful for your own AKS solution whether that be a custom AKS training experience or something else. Thanks for reading.

Cloud Platform Architect. Opinions and articles on medium are my own.