Installing the Microk8s snap couldn’t be much easier. However there are a couple of extra steps and gotchas if you want to install this in a VM on the DigitalOcean.
1 snap install microk8s --classic
You can alias the
commands if you don’t want to keep running
snap alias microk8s.kubectl kubectl
snap alias microk8s.helm helm
Microk8s makes it simple to enable common add-ons the ones we are enabling
# Dashboard for a bit of a nice interface to see what's happening
# Ingress for managing domain names
# Helm so we can install services from templates
When we want to get to our dashboard we can’t login over http, so we need proxy connections to our local workstation. For this we will need to install
locally, luckily this is also available as a snap, so we can install that with a
snap install kubectl
To get the config for your local
you can run another handy command
this will print a config file to the terminal that you can copy the into
then you can run
Before you run the proxy command you can get your access token by running.
1 kubectl -n kube-system describe secret $(kubectl -n kube-system get secret | grep default-token | cut -d " " -f1)
Now we have setup
locally you can run
to access your cluster from localhost. The URL to your dashboard will be
A service broker is a way of provisioning services and binding them to applications. With a service broker you can provision a database and bind it to a deployment.
After Ade Attwood’s recent dive into TLS and creating server certificates with a root ca. This is a much simpler way with mkcert…
This post is a version of a recent lecture. The question is “What skills and knowledge might future designers be expected to know”.