Skip to content

Commit 7baa641

Browse files
authored
Add microk8s to foundational.md
Adding microk8s as credible and stable alternative to get started with Kubernetes on a local machine. This is especially attractive for those not wanting to incur the overhead of running a VM for a local cluster.
1 parent 797db72 commit 7baa641

1 file changed

Lines changed: 19 additions & 0 deletions

File tree

content/en/docs/user-journeys/users/application-developer/foundational.md

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -53,6 +53,25 @@ Minikube can be installed locally, and runs a simple, single-node Kubernetes clu
5353

5454
You can get basic information about your cluster with the commands `kubectl cluster-info` and `kubectl get nodes`. However, to get a good idea of what's really going on, you need to deploy an application to your cluster. This is covered in the next section.
5555

56+
#### microk8s
57+
58+
On Linux, *microk8s* might be a good alternative for a local install of upstream Kubernetes. Microk8s keeps up with the current Kubernetes, and auto-updates to the latest point release for your convenience. Microk8s does not require you to install a hypervisor or launch a virtual machine, and installs within ~30 seconds.
59+
60+
* {{< link text="Install microk8s" url="https://microk8s.io/" >}}.
61+
62+
Once you have installed microk8s, using the prefix "microk8s." you can tab-complete a variety of commands, including accessing the included registry, container runtime and more (for example, `microk8s.kubectl`). Using the prefix ensures clean separation of the local environment vs other Kubernetes API endpoints.
63+
64+
It also includes commands to `microk8s.enable`
65+
66+
* the Kubernetes Dashboard
67+
* the DNS service
68+
* GPU passthrough (for NVIDIA)
69+
* Ingress
70+
* Istio
71+
* Metrics server
72+
* Registry
73+
* Storage
74+
5675
## Deploy an application
5776

5877
#### Basic workloads

0 commit comments

Comments
 (0)