I\u2019m using Proxmox<\/a> as a virtualisation platform on this mini PC, and I\u2019ve chosen SUSE Leap 15.6 as the operating system for the virtual machine that will host my RKE2 installation.<\/p>\n\n\n\n First, I created a VM and dedicated some resources to my instance.<\/p>\n\n\n\n SUSE recommends at least 8GB of RAM and 4vCPU for RKE2 to run smoothly.<\/p>\n\n\n\n Let\u2019s start with that, I can adjust later if the system struggles.<\/p>\n\n\n\n I added 50GB of storage, that should be more than enough (that\u2019s a lot of storage, we really don\u2019t need that much for the YaK itself, but I might reuse this VM for other purposes too)<\/p>\n\n\n\n I\u2019m passing the installation steps of SUSE Leap in server mode, as they are straightforward. First of all, we need to install the following packages on the VM hosting the YaK:<\/p>\n\n\n\n Let\u2019s check what is already installed by default with SUSE Leap 15.6:<\/p>\n\n\n As you can see, Tar<\/strong> is already installed but not Git<\/strong> nor Helm<\/strong>. Let\u2019s install them:<\/p>\n\n\n As a pre-requisite<\/a>, Firewalld must be stopped. Firewalld is active. I need to stop and disable the service so that it does not restart at system startup:<\/p>\n\n\n Next, I installed RKE2. To do so, I simply followed the official procedure: https:\/\/docs.rke2.io\/install\/quickstart<\/a><\/p>\n\n\n As mentioned in the RKE2 documentation: \u201cadditional utilities will be installed at I\u2019m adding the repository to my default PATH (this step can be done temporarily or permanently, by editing your RKE2 install writes a kubeconfig file to I check that the Kubernetes cluster is up and pods are running:<\/p>\n\n\n We need some storage, don’t we? Alright, I now have a fully functional Kubernetes cluster. Finally, let’s connect to our web app!<\/p>\n\n\n\n Voil\u00e0!!<\/p>\n\n\n\n I\u2019ve now got a local YaK on RKE2 running at home, ready to deploy infrastructures, servers and components wherever I want.<\/p>\n\n\n\n For more info about the YaK, visit yak4all.io<\/a><\/p>\n\n\n\n And if you can’t be bothered installing your own YaK, you can bring up a fully functional YaK demo environment, within minutes : yak4all.io\/demo<\/a> Happy YaKing \ud83d\ude09 !<\/p>\n","protected":false},"excerpt":{"rendered":" I bought a mini PC last year and I use it as a home lab to test things and play around.So I thought, why not install a RKE2 Kubernetes cluster and deploy my own YaK instance on it? Let\u2019s dive-in. In this article, I will explain how I installed a single node Kubernetes cluster with […]<\/p>\n","protected":false},"author":83,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[2721],"tags":[2716,2634],"type_dbi":[],"class_list":["post-39390","post","type-post","status-publish","format-standard","hentry","category-yak","tag-yak","tag-kubernetes-2"],"acf":[],"yoast_head":"\nCreate my VM in Proxmox<\/h2>\n\n\n\n
![\"\"](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2025\/07\/image-9.png\")
<\/figure>\n\n\n\n
But, just in case, I’m adding the links to Proxmox<\/a> and to SUSE Leap<\/a> install docs here.<\/p>\n\n\n\nInstall packages<\/h2>\n\n\n\n
\n
\nlocalhost:~ # zypper se --installed-only tar\nLoading repository data...\nReading installed packages...\n\nS | Name | Summary | Type\n---+-------------------------+--------------------------------------------------+--------\ni | cantarell-fonts | Contemporary Humanist Sans Serif Font | package\ni | deltarpm | Tools to Create and Apply deltarpms | package\ni | shared-python-startup | Startup script shared by all Python interpreters | package\ni | star | POSIX.1-2001-Compliant Tar Implementation | package\ni | star-rmt | Magnetic tape control and server | package\ni | tar | GNU implementation of ((t)ape (ar)chiver) | package\ni | tar-lang | Translations for package tar | package\ni | tar-rmt | Remote tape drive control server by GNU | package\ni | zypper-needs-restarting | needs-restarting compatibility with zypper | package\n\nlocalhost:~ # zypper se --installed-only git\nLoading repository data...\nReading installed packages...\nNo matching items found.\n\nlocalhost:~ # zypper se --installed-only helm\nLoading repository data...\nReading installed packages...\nNo matching items found.\n<\/pre><\/div>\n\n\n
\nlocalhost:~ # zypper install git\nlocalhost:~ # zypper install helm\n<\/pre><\/div>\n\n\n
Stop firewalld<\/h2>\n\n\n\n
Let\u2019s check its status:<\/p>\n\n\n\nlocalhost:~ # systemctl status firewalld\n\u25cf firewalld.service - firewalld - dynamic firewall daemon\n Loaded: loaded (\/usr\/lib\/systemd\/system\/firewalld.service; enabled; preset: disabled)\n Active: active (running) since Wed 2025-04-30 12:12:43 CEST; 2h 7min ago\n Docs: man:firewalld(1)\n Main PID: 743 (firewalld)\n Tasks: 2 (limit: 4915)\n CPU: 349ms\n CGroup: \/system.slice\/firewalld.service\n \u2514\u2500743 \/usr\/bin\/python3 \/usr\/sbin\/firewalld --nofork --nopid\n\nApr 30 12:12:43 localhost systemd[1]: Starting firewalld - dynamic firewall daemon...\nApr 30 12:12:43 localhost systemd[1]: Started firewalld - dynamic firewall daemon.\n\n<\/pre><\/div>\n\n\n
\nlocalhost:~ # systemctl stop firewalld\nlocalhost:~ # systemctl disable firewalld\n<\/pre><\/div>\n\n\n
Install RKE2<\/h2>\n\n\n\n
\nlocalhost:~ # curl -sfL https:\/\/get.rke2.io | sh -\nlocalhost:~ # systemctl enable rke2-server.service\nlocalhost:~ # systemctl start rke2-server.service\n\n<\/pre><\/div>\n\n\n
\/var\/lib\/rancher\/rke2\/bin\/<\/code>. They include: kubectl, crictl, and ctr.
Note that these are not on your path by default.\u201d<\/em><\/p>\n\n\n\n~\/.bashrc file<\/code>). I chose to make it permanent by editing my ~\/.bashrc file<\/code>, but it\u2019s up to you.<\/p>\n\n\n\nexport PATH="\/var\/lib\/rancher\/rke2\/bin:$PATH"\n<\/pre><\/div>\n\n\n
\/etc\/rancher\/rke2\/rke2.yaml<\/code>.<\/strong>
Again, I\u2019m adding this into my ~\/.bashrc<\/code> file<\/p>\n\n\n\nexport KUBECONFIG=\/etc\/rancher\/rke2\/rke2.yaml\n<\/pre><\/div>\n\n\n
\nlocalhost:~ # kubectl get nodes\nNAME STATUS ROLES AGE VERSION\nlocalhost Ready control-plane,etcd,master 22m v1.31.7+rke2r1\n\nlocalhost:~ # kubectl get pods -A\nNAMESPACE NAME READY STATUS RESTARTS AGE\nkube-system cloud-controller-manager-localhost 1\/1 Running 1 (23m ago) 22m\nkube-system etcd-localhost 1\/1 Running 0 22m\nkube-system helm-install-rke2-canal-nxphw 0\/1 Completed 0 23m\nkube-system helm-install-rke2-coredns-2whps 0\/1 Completed 0 23m\nkube-system helm-install-rke2-ingress-nginx-9mpwb 0\/1 Completed 0 23m\nkube-system helm-install-rke2-metrics-server-t8g27 0\/1 Completed 0 23m\nkube-system helm-install-rke2-runtimeclasses-nbq2v 0\/1 Completed 0 23m\nkube-system helm-install-rke2-snapshot-controller-crd-fmwqh 0\/1 Completed 0 23m\nkube-system helm-install-rke2-snapshot-controller-nqq5g 0\/1 Completed 1 23m\nkube-system kube-apiserver-localhost 1\/1 Running 0 22m\nkube-system kube-controller-manager-localhost 1\/1 Running 0 22m\nkube-system kube-proxy-localhost 1\/1 Running 0 22m\nkube-system kube-scheduler-localhost 1\/1 Running 0 22m\nkube-system rke2-canal-qlk8b 2\/2 Running 0 22m\nkube-system rke2-coredns-rke2-coredns-autoscaler-596dcdf688-dsjjz 1\/1 Running 0 22m\nkube-system rke2-coredns-rke2-coredns-cf7df985b-zqwqn 1\/1 Running 0 22m\nkube-system rke2-ingress-nginx-controller-b52nh 1\/1 Running 0 21m\nkube-system rke2-metrics-server-58ff89f9c7-dndfb 0\/1 Running 0 21m\nkube-system rke2-snapshot-controller-58dbcfd956-srw5z 1\/1 Running 0 21m\n\n<\/pre><\/div>\n\n\n
Add a persistent volume<\/h2>\n\n\n\n
By default, RKE2 does not provide persistent volumes.
However, \u201cLocal Path Provisioner\u201d provides a way for the Kubernetes users to utilize the local storage in each node (https:\/\/github.com\/rancher\/local-path-provisioner<\/a>). Let’s use that.<\/p>\n\n\n\nlocalhost:~ # kubectl apply -f https:\/\/raw.githubusercontent.com\/rancher\/local-path-provisioner\/v0.0.31\/deploy\/local-path-storage.yaml\nnamespace\/local-path-storage created\nserviceaccount\/local-path-provisioner-service-account created\nrole.rbac.authorization.k8s.io\/local-path-provisioner-role created\nclusterrole.rbac.authorization.k8s.io\/local-path-provisioner-role created\nrolebinding.rbac.authorization.k8s.io\/local-path-provisioner-bind created\nclusterrolebinding.rbac.authorization.k8s.io\/local-path-provisioner-bind created\ndeployment.apps\/local-path-provisioner created\nstorageclass.storage.k8s.io\/local-path created\nconfigmap\/local-path-config created\n<\/pre><\/div>\n\n\n
Install YaK<\/h2>\n\n\n\n
Let\u2019s install the YaK on it now.<\/p>\n\n\n\n\n
\nkubectl create ns yak\n<\/pre><\/div>\n\n\n
\n
\nhelm repo add yak https:\/\/gitlab.com\/api\/v4\/projects\/63133284\/packages\/helm\/stable && helm repo update\n<\/pre><\/div>\n\n\n
\n
\nlocalhost:~ # vi yak.values.yaml\n<\/pre><\/div>\n\n
\nglobal:\n hostname: yak.lab\n admin_credentials:\n password: "ABCdef1234@" #default password to be changed to your need\n\nyak-postgres:\n postgresPassword: "" # Randomly generated if not set\n persistence:\n size: 20Gi\n storageClassName: "local-path" # Uses default if empty\n\nyak-graphile:\n # Archive storage stores the component types archives at import time\n persistence: &archives_storage\n size: 20Gi\n storageClassName: "local-path" # Uses default if empty\n # If using a multi-node cluster, uncomment these 2 lines:\n #accessModes:\n # - ReadWriteMany\n\n # If you want to expose the rest API at https:\/\/hostname\/data\/graphql and have the postgraphile UI at https:\/\/yak.my-domain.local\/data\/graphiql\n ingress:\n enabled: true\n className: "" # Uses default if empty\n tls:\n - secretName: yak-tls-secret\n hosts:\n - yak.lab\n\nyak-runner:\n image:\n pullPolicy: Always\n persistence:\n # Runner shares the archives storage with graphile\n graphile: *archives_storage\n components:\n enabled: true\n storageClassName: "local-path" # Uses default if empty\n size: 8Gi\n sshconfig:\n enabled: true\n storageClassName: "local-path" # Uses default if empty\n size: 1Gi\n\nyak-ui:\n # Mandatory if you want to access the UI through ingress\n ingress:\n enabled: true\n className: "" # Uses default if empty\n tls:\n - secretName: yak-tls-secret\n hosts:\n - yak.lab\n\n<\/pre><\/div>\n\n\n
\n
\nhelm install yak yak\/yak -f yak.values.yaml -n yak\n<\/pre><\/div>\n\n\n
\n
\nlocalhost:~ # kubectl get pods -n yak\nNAME READY STATUS RESTARTS AGE\nyak-graphile-5b5454fd64-hmk2c 1\/1 Running 0 1m\nyak-postgres-7bcf4f9897-7mrdg 1\/1 Running 0 1m\nyak-runner-6669948599-9ggwn 1\/1 Running 0 1m\nyak-ui-7f6d77c765-spgfn 1\/1 Running 0 1m\n\n<\/pre><\/div>\n\n\n
Connect to the YaK with https<\/h2>\n\n\n\n
\n
\/etc\/hosts<\/code> file and add your YaK server, in my case:<\/li>\n<\/ul>\n\n\n\n192.168.10.185 yak.lab\n<\/pre><\/div>\n\n\n
\n
\n
\n
![\"YaK](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2025\/07\/image-15.png\")
<\/figure>\n\n\n\n![\"YaK](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2025\/07\/image-16.png\")
<\/figure>\n\n\n\n
Feel free to play around and explore our use cases<\/a> <\/p>\n\n\n\n