Deploying a Kubernetes Cluster with Minikube on Debian 11

I’m using a Hetzner dedicated server here, but a VPS works as well.

1
 CPU 型号          : Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz
2
 CPU 核心数        : 1 物理核心, 4 总核心, 8 总线程数
3
 CPU 频率          : 4089.603 MHz
4
 CPU 缓存          : L1: 256.00 KB / L2: 1.00 MB / L3: 8.00 MB
5
 硬盘空间          : 678.17 GiB / 936.60 GiB
6
 启动盘路径        : /dev/md1
7
 内存              : 24.31 GiB / 62.59 GiB
8
 Swap              : [ no swap partition or swap file detected ]
9
 系统在线时间      : 14 days, 19 hour 25 min
10
 负载              : 1.42, 1.76, 2.01
11
 系统              : Debian GNU/Linux 11 (bullseye) (x86_64)
12
 AES-NI指令集      : ✔ Enabled
13
 VM-x/AMD-V支持    : ✔ Enabled
14
 架构              : x86_64 (64 Bit)
15
 内核              : 5.10.0-23-amd64
16
 TCP加速方式       : bbr
17
 虚拟化架构        : Dedicated
18
 NAT类型           : 开放型
19
 IPV4 ASN          : AS24940 Hetzner Online GmbH
20
 IPV4 位置         : Berlin / Berlin / DE
21
 IPV6 ASN          : AS24940 Hetzner Online GmbH
22
 IPV6 位置         : Nuremberg / DE-BY

Environment preparation#
2 CPUs or more
2GB of free memory
20GB of free disk space
Internet connection
Container or virtual machine manager, such as: Docker, QEMU, Hyperkit, Hyper-V, KVM, Parallels, Podman, VirtualBox, or VMware Fusion/Workstation

Install Kubectl#

1
依次执行
2
curl -LO "https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl"
3
chmod +x ./kubectl
4
sudo mv kubectl /usr/local/bin/
5

6
### 检查Kubectl是否安装成功
7
kubectl version -o yaml

Install Minikube#

1
依次执行
2
curl -LO https://storage.googleapis.com/minikube/releases/latest/minikube-darwin-amd64
3
sudo install minikube-darwin-amd64 /usr/local/bin/minikube
4
检查是否安装成功
5
minikube version

Start Minikube#

1
我这边采用的是Root权限下启动需要执行的，如果直接minikube启动，会有权限警告错误
2
minikube start --driver=docker --force

Error summary#

When logged in as root, starting the cluster directly with minikube start shows:

1
minikube v1.31.2 on Debian 11.7
2
Automatically selected the docker driver. Other choices: ssh, none
3
The "docker" driver should not be used with root privileges. If you wish to continue as root, use --force.
4
If you are running minikube within a VM, consider using --driver=none:
5
https://minikube.sigs.k8s.io/docs/reference/drivers/none/
6
X Exiting due to DRV_AS_ROOT: The "docker" driver should not be used with root privileges.

Solutions:

Switch to a non-root user.
Start the cluster with minikube start --driver=docker --force.

Check cluster status#

1
kubectl cluster-info

Check running nodes#

1
kubectl get nodes

Access the Minikube container#

1
minikube ssh

Exit the container shell:

1
exit

Stop and delete the Kubernetes cluster#

1
minikube stop
2
minikube delete

Check Minikube status#

1
minikube status

Access the Minikube Kubernetes Dashboard#

By default, Minikube provides a web UI you can use to manage your cluster.

You can list all Minikube addons with the following command: minikube addons list

You’ll see output similar to this:

1
[15:56 root@panel ~] > minikube addons list
2
|-----------------------------|----------|--------------|--------------------------------|
3
|         ADDON NAME          | PROFILE  |    STATUS    |           MAINTAINER           |
4
|-----------------------------|----------|--------------|--------------------------------|
5
| ambassador                  | minikube | disabled     | 3rd party (Ambassador)         |
6
| auto-pause                  | minikube | disabled     | minikube                       |
7
| cloud-spanner               | minikube | disabled     | Google                         |
8
| csi-hostpath-driver         | minikube | disabled     | Kubernetes                     |
9
| dashboard                   | minikube | disabled     | Kubernetes                     |
10
| default-storageclass        | minikube | enabled ✅   | Kubernetes                     |
11
| efk                         | minikube | disabled     | 3rd party (Elastic)            |
12
| freshpod                    | minikube | disabled     | Google                         |
13
| gcp-auth                    | minikube | disabled     | Google                         |
14
| gvisor                      | minikube | disabled     | minikube                       |
15
| headlamp                    | minikube | disabled     | 3rd party (kinvolk.io)         |
16
| helm-tiller                 | minikube | disabled     | 3rd party (Helm)               |
17
| inaccel                     | minikube | disabled     | 3rd party (InAccel             |
18
|                             |          |              | [[email protected]])            |
19
| ingress                     | minikube | disabled     | Kubernetes                     |
20
| ingress-dns                 | minikube | disabled     | minikube                       |
21
| inspektor-gadget            | minikube | disabled     | 3rd party                      |
22
|                             |          |              | (inspektor-gadget.io)          |
23
| istio                       | minikube | disabled     | 3rd party (Istio)              |
24
| istio-provisioner           | minikube | disabled     | 3rd party (Istio)              |
25
| kong                        | minikube | disabled     | 3rd party (Kong HQ)            |
26
| kubevirt                    | minikube | disabled     | 3rd party (KubeVirt)           |
27
| logviewer                   | minikube | disabled     | 3rd party (unknown)            |
28
| metallb                     | minikube | disabled     | 3rd party (MetalLB)            |
29
| metrics-server              | minikube | disabled     | Kubernetes                     |
30
| nvidia-driver-installer     | minikube | disabled     | 3rd party (Nvidia)             |
31
| nvidia-gpu-device-plugin    | minikube | disabled     | 3rd party (Nvidia)             |
32
| olm                         | minikube | disabled     | 3rd party (Operator Framework) |
33
| pod-security-policy         | minikube | disabled     | 3rd party (unknown)            |
34
| portainer                   | minikube | disabled     | 3rd party (Portainer.io)       |
35
| registry                    | minikube | disabled     | minikube                       |
36
| registry-aliases            | minikube | disabled     | 3rd party (unknown)            |
37
| registry-creds              | minikube | disabled     | 3rd party (UPMC Enterprises)   |
38
| storage-provisioner         | minikube | enabled ✅   | minikube                       |
39
| storage-provisioner-gluster | minikube | disabled     | 3rd party (Gluster)            |
40
| volumesnapshots             | minikube | disabled     | Kubernetes                     |
41
|-----------------------------|----------|--------------|--------------------------------|

Next, list all running pod images in the cluster with:

1
kubectl get pods --all-namespaces

Now run the following command to get the Kubernetes Dashboard URL:

1
minikube dashboard --url

At this point, the Minikube Dashboard is installed and running on port 39509 on the server. However, it is only accessible from the local address. To access it from outside, run the following command:

1
kubectl proxy --address='0.0.0.0' --disable-filter=true

Now open Chrome and visit:
http://your-server-ip:8001/api/v1/namespaces/kubernetes-dashboard/services/http:kubernetes-dashboard:/proxy/.
You will be redirected to the Kubernetes Dashboard, as shown below: