Cloud Native 3 min read

Kubernetes Cluster Host Planning and Deployment Steps

This guide outlines host planning for a master and two worker nodes, specifies CentOS, Docker, and Kubernetes version requirements, and provides step‑by‑step deployment instructions—including image download, network initialization, Flannel setup, and verification of pod and node status—illustrated with diagrams and screenshots.

DevOps Cloud Academy
DevOps Cloud Academy
DevOps Cloud Academy
Kubernetes Cluster Host Planning and Deployment Steps

Host Planning

The master node is allocated 2 CPU cores and 8 GB RAM with hostname master.example.com and IP 192.168.0.20; two worker nodes (node1 and node2) each receive 2 CPU/4 GB RAM, hostnames node1.example.com, node2.example.com, and IPs 192.168.0.49 and 192.168.0.50 respectively.

Software Requirements

Operating system: CentOS Linux 7.3.1611 (Core). Docker version 1.13.1 (build 07f3374/1.13.1). Kubernetes version v1.13.1.

Deployment Steps

The architecture diagram is shown below.

All nodes execute a common script:

https://raw.githubusercontent.com/zeyangli/devops/master/allrun.sh

. The master node downloads images, initializes the network, configures kubectl and the Flannel overlay network, and then validates the status of all pods and nodes. Screenshots illustrate each stage, including master configuration, node addition, and verification.

Adding Node Workers

Verification screenshots follow.

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.

DockerKubernetesCluster DeploymentCentOSHost Planning
DevOps Cloud Academy
Written by

DevOps Cloud Academy

Exploring industry DevOps practices and technical expertise.

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.