Cloud Native 9 min read

Step‑by‑Step: Install Docker Desktop, Enable Kubernetes, Add Kuboard, and Deploy Nginx

This guide walks you through installing Docker Desktop on Windows, activating a single‑node Kubernetes cluster, deploying the Kuboard management UI, and finally creating and testing an Nginx deployment using Kuboard’s graphical interface and command‑line tools.

Open Source Tech Hub
Open Source Tech Hub
Open Source Tech Hub
Step‑by‑Step: Install Docker Desktop, Enable Kubernetes, Add Kuboard, and Deploy Nginx

Install Docker Desktop

Download the Docker Desktop installer for Windows from the official Docker website and run Docker Desktop Installer.exe. During installation enable either Enable Hyper‑V Windows Features or Install required Windows components for WSL 2. After the wizard finishes, optionally configure a mirror registry by adding a {"registry-mirrors":["https://your.mirror.aliyuncs.com"]} entry to the Docker settings. Verify the installation with docker version or docker -v.

Enable a Single‑Node Kubernetes Cluster

Open Docker Desktop, go to Settings → Kubernetes, and toggle the switch to start the built‑in Kubernetes cluster. After the cluster starts, the status shows Running or Active. The kubectl CLI is automatically configured; confirm the cluster is reachable with kubectl cluster-info.

Install Kuboard (v3)

Run the following Docker command to start Kuboard v3 with built‑in user database:

docker run -d \
  --restart=unless-stopped \
  --name=kuboard \
  -p 8089:80/tcp \
  -p 10081:10081/tcp \
  -e KUBOARD_ENDPOINT="http://192.168.3.29:8089" \
  -e KUBOARD_AGENT_SERVER_TCP_PORT="10081" \
  -v d:\k8s:/data \
  eipwork/kuboard:v3

Use a faster image if desired, e.g. swr.cn-east-2.myhuaweicloud.com/kuboard/kuboard:v3. Do not use 127.0.0.1 or localhost as the internal IP; Kuboard and the Kubernetes cluster should be on different subnets. Access the UI at http://127.0.0.1:8089/ and log in with username admin and password Kuboard123.

Add the Docker Desktop Cluster to Kuboard

In Kuboard, choose “Add Cluster” and select the Kuboard Agent method. Provide a name (e.g., Tinywan‑k8s) and an agent deployment name ( kuboard-agent-tinywan). Download the agent manifest with:

curl -k 'http://192.168.3.29:8089/kuboard-api/cluster/Tinywan-k8s/kind/KubernetesCluster/Tinywan-k8s/resource/installAgentToKubernetes?token=YOUR_TOKEN' > kuboard-agent.yaml

Apply the manifest to the cluster: kubectl apply -f .\kuboard-agent.yaml The command creates the necessary namespace, service accounts, role bindings, and the agent deployment. Once the agent reports a Ready status, the cluster appears in Kuboard.

Deploy an Nginx Application via Kuboard

Select the default namespace and click “Create Workload”. Fill in the basic information and container details:

Container name: tinywan2024nginx Image: nginx:1.26.0-alpine Port: 80 Save the workload. Kuboard shows the deployment result; you can test it by clicking the “Proxy” button, which opens the Nginx service through the Kuboard proxy.

Verify the Deployment

Use the following curl command to access the pod through the proxy:

curl -X GET -i \
  --cookie "KuboardToken=YOUR_TOKEN; KuboardProxy=..." \
  http://127.0.0.1:8089/k8s-proxy/Tinywan-k8s/api/v1/namespaces/default/pods/http:tinywan20240428-748cc6b49b-qtlcn:80/proxy/

Modify the served index.html if desired, then re‑access the URL to see the changes.

Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

DeploymentKubernetesNGINXkuboard
Open Source Tech Hub
Written by

Open Source Tech Hub

Sharing cutting-edge internet technologies and practical AI resources.

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.