{"id":3151,"date":"2024-04-11T12:37:17","date_gmt":"2024-04-11T16:37:17","guid":{"rendered":"https:\/\/dft.wiki\/?p=3151"},"modified":"2024-09-08T09:58:46","modified_gmt":"2024-09-08T13:58:46","slug":"microk8s-the-out-of-the-box-kubernetes-of-ubuntu","status":"publish","type":"post","link":"https:\/\/dft.wiki\/?p=3151","title":{"rendered":"MicroK8S, the Out-of-the-box Kubernetes of Ubuntu"},"content":{"rendered":"

\"\"<\/p>\n

MicroK8s<\/strong> is the Canonical single-package fully conformant<\/span> lightweight Kubernetes [Link<\/a>]. It means, it is a 100% compatible Kubernetes orchestrator that can be deployed with a “single-click” on Ubuntu and many other distributions via Snap.<\/p>\n

When compared with MiniKube<\/strong> [Link<\/a>] and K3s<\/strong> [Link<\/a>], MicroK8s<\/strong> is a minimal production Kubernetes that offers with the minimal effort for operating (low-ops).<\/p>\n

Kubernetes<\/strong> is a beast created by Google to meet Google needs of scalability, that is why it is a common knowledge that Kubernetes is Hard to deploy and manage. This makes many companies opt for managed services such as EKS<\/strong> (from AWS), GKE<\/strong> (from GCP), or AKS<\/strong> (from Azure). And that comes with an associated price tag.<\/p>\n

Most of the use cases for orchestrating clusters of containers are very simple and MicroK8s<\/strong> suits these requirements by far.<\/p>\n

\n

INSTALLATION<\/strong><\/p>\n

sudo snap install microk8s --classic\r\nmicrok8s.inspect<\/pre>\n
That is it!<\/strong> Even kubectl<\/code> is included in the package.<\/p>\n
To use MicroK8s without sudo<\/code>,add your username to the microk8s<\/code> group.<\/p>\n
sudo usermod -a -G microk8s userName<\/pre>\n
Stopping and starting the\u00a0 MicroK8s Deamon.<\/p>\n
microk8s.stop\r\nmicrok8s.start<\/pre>\n
\n
BASIC COMMANDS<\/strong><\/p>\n
sudo microk8s kubectl get nodes\r\nsudo microk8s kubectl get services<\/pre>\n
To avoid repetition, here is another post that show cases standard Kubernetes commands and use cases [Link<\/a>].<\/p>\n
\n
EXTENDED FEATURES<\/strong><\/p>\n
Enabling popular Addons.<\/p>\n
sudo microk8s enable dashboard\r\nsudo microk8s enable registry\r\nsudo microk8s enable ingress\r\nsudo microk8s enable dns\r\nsudo microk8s enable gpu\r\nsudo microk8s enable ha-cluster\r\nsudo microk8s enable cert-manager\r\nsudo microk8s enable prometheus\r\nsudo microk8s enable community\r\nsudo microk8s enable istio<\/pre>\n
\n
ACCESSING THE DASHBOARD<\/strong><\/p>\n
sudo microk8s enable dashboard\r\nsudo microk8s kubectl create token default<\/pre>\n
\"\"<\/p>\n
By default, the token expires in 1 hour. If necessary, give it more time or add the namespace:<\/p>\n
sudo microk8s kubectl create token default --namespace=namespace<\/strong> --duration=24h<\/strong><\/pre>\n
Now, expose the dashboard.<\/p>\n
sudo microk8s kubectl port-forward -n kube-system service\/kubernetes-dashboard 10443:443<\/pre>\n
Navigate to https:\/\/127.0.0.1:10443<\/a> and paste generated token:<\/p>\n
\"\"<\/p>\n
\"\"<\/p>\n
 Note:<\/strong> this dashboard is not specific from MicroK8s. Instead, it is a Kubernetes module and is not in the scope of this post to walk-through the Dashboard. Check our the Dashboard Walk-through post at [Link<\/a>].<\/p>\n
\n
RUNNING MICROK8S IN PROXMOX LXC<\/strong><\/p>\n
Create a new CT and uncheck the option for “unprivileged”.<\/p>\n
\"\"<\/p>\n
Before starting the CT for the first time, on open a shell on the host and edit the CT configuration file.<\/p>\n
nano \/etc\/pve\/nodes\/proxmox\/lxc\/100.conf<\/pre>\n
lxc.apparmor.profile: unconfined\r\nlxc.cap.drop:\r\nlxc.mount.auto: proc:rw sys:rw\r\nlxc.mount.entry: \/dev\/fuse dev\/fuse none bind,create=file 0 0\r\nlxc.mount.entry: \/sys\/kernel\/security sys\/kernel\/security none bind,create=file 0 0<\/pre>\n
Then, start the CT and add the following line to the crontab of the root user.<\/p>\n
crontab -e<\/pre>\n
@reboot ln -s \/dev\/console \/dev\/kmsg<\/pre>\n
Setup the environment.<\/p>\n
ln -s \/dev\/console \/dev\/kmsg\r\napt update && apt upgrade -y\r\napt install snapd squashfuse fuse -y\r\nreboot<\/pre>\n
Now, the installation can happen.<\/p>\n
snap install microk8s --classic\r\napparmor_parser --add \/var\/lib\/snapd\/apparmor\/profiles\/snap.microk8s.*\r\nmicrok8s.inspect\r\nreboot<\/pre>\n
After rebooting, check if it is still working as expected.<\/p>\n
microk8s.inspect\r\nmicrok8s kubectl get nodes\r\nmicrok8s kubectl get services\r\n<\/pre>\n
\n
BONUS<\/strong><\/p>\n
Auto-start Microk8s<\/strong> and it’s the dashboard on startup.<\/p>\n
nano \/etc\/systemd\/system\/kubectl.service<\/pre>\n
[Unit]\r\nDescription=Port forward for Kubernetes Dashboard\r\nAfter=network.target\r\n\r\n[Service]\r\nExecStart=\/root\/microk8s.sh\r\nRestart=always\r\nUser=root\r\n\r\n[Install]\r\nWantedBy=multi-user.target<\/pre>\n
nano \/root\/microk8s.sh\r\nchmod +x \/root\/microk8s.sh<\/pre>\n
#!\/bin\/bash\r\napparmor_parser --add \/var\/lib\/snapd\/apparmor\/profiles\/snap.microk8s.*\r\nmicrok8s.start\r\nsleep 30\r\n\/snap\/bin\/microk8s kubectl port-forward -n kube-system service\/kubernetes-dashboard 10443:443 --address 0.0.0.0<\/pre>\n
systemctl daemon-reload\r\nsystemctl enable kubectl --now<\/pre>\n
\n
OTHER POSTS<\/strong><\/p>\n
Minikube<\/strong> on Ubuntu 22.04 [Link<\/a>].<\/p>\n
K3s<\/strong> on Ubuntu 22.04 [Link<\/a>].<\/p>\n
K8s<\/strong> Persistent Volumes [Link<\/a>].<\/p>\n
K8s<\/strong> Cheat Sheet [Link<\/a>].<\/p>\n
K8s<\/strong> Dashboard [Link<\/a>].<\/p>\n","protected":false},"excerpt":{"rendered":"
MicroK8s is the Canonical single-package fully conformant lightweight Kubernetes [Link]. It means, it is a […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[],"class_list":["post-3151","post","type-post","status-publish","format-standard","hentry","category-linux"],"_links":{"self":[{"href":"https:\/\/dft.wiki\/index.php?rest_route=\/wp\/v2\/posts\/3151","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dft.wiki\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dft.wiki\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dft.wiki\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/dft.wiki\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=3151"}],"version-history":[{"count":18,"href":"https:\/\/dft.wiki\/index.php?rest_route=\/wp\/v2\/posts\/3151\/revisions"}],"predecessor-version":[{"id":4421,"href":"https:\/\/dft.wiki\/index.php?rest_route=\/wp\/v2\/posts\/3151\/revisions\/4421"}],"wp:attachment":[{"href":"https:\/\/dft.wiki\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=3151"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dft.wiki\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=3151"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dft.wiki\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=3151"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}