You are viewing documentation for KubeSphere version:v3.0.0

KubeSphere v3.0.0 documentation is no longer actively maintained. The version you are currently viewing is a static snapshot. For up-to-date documentation, see the latest version.

Last updated:

Edit

Feedback

Deploy Kubernetes and Kubesphere on Bare Metal

Introduction

In addition to the deployment on cloud, KubeSphere can also be installed on bare metal. As the virtualization layer is removed, the infrastructure overhead is drastically reduced, which brings more compute and storage resources to app deployments. As a result, hardware efficiency is improved. Refer to the example below to deploy KubeSphere on bare metal.

Prerequisites

Make sure you already know how to install KubeSphere on a multi-node cluster based on the tutorial Multi-node Installation.
Server and network redundancy in your environment.
For a production environment, it is recommended that you prepare persistent storage and create a StorageClass in advance. For development and testing, you can use the integrated OpenEBS to provision LocalPV as the storage service directly.

Prepare Linux Hosts

This tutorial uses 3 physical machines of DELL 620 Intel (R) Xeon (R) CPU E5-2640 v2 @ 2.00GHz (32G memory), on which CentOS Linux release 7.6.1810 (Core) will be installed for the minimal deployment of KubeSphere.

Install CentOS

Download and install the image first. Make sure you allocate at least 200 GB to the root directory where it stores docker images (you can skip this if you are installing KubeSphere for testing).

For more information about the supported systems, see System Requirements.

Here is a list of the three hosts for your reference.

Host IP	Host Name	Role
192.168.60.152	master1	master1, etcd
192.168.60.153	worker1	worker
192.168.60.154	worker2	worker

NIC settings

Clear NIC configurations.

ifdown em1

ifdown em2

rm -rf /etc/sysconfig/network-scripts/ifcfg-em1

rm -rf /etc/sysconfig/network-scripts/ifcfg-em2

Create the NIC bonding.

nmcli con add type bond con-name bond0 ifname bond0 mode 802.3ad ip4 192.168.60.152/24 gw4 192.168.60.254

Set the bonding mode.

nmcli con mod id bond0 bond.options mode=802.3ad,miimon=100,lacp_rate=fast,xmit_hash_policy=layer2+3

Bind the physical NIC.

nmcli con add type bond-slave ifname em1 con-name em1 master bond0

nmcli con add type bond-slave ifname em2 con-name em2 master bond0

Change the NIC mode.

vi /etc/sysconfig/network-scripts/ifcfg-bond0
BOOTPROTO=static

Restart Network Manager.

systemctl restart NetworkManager

nmcli con # Display NIC information

Change the host name and DNS.

hostnamectl set-hostname worker-1

vim /etc/resolv.conf

Time settings

Synchronize time.

yum install -y chrony

systemctl enable chronyd

systemctl start chronyd

timedatectl set-ntp true

Set the time zone.
```
timedatectl set-timezone Asia/Shanghai
```
Check if the ntp-server is available.
```
chronyc activity -v
```

Firewall settings

Execute the following commands to stop and disable the FirewallD service:

iptables -F

systemctl status firewalld

systemctl stop firewalld

systemctl disable firewalld

Package updates and dependencies

Execute the following commands to update system packages and install dependencies.

yum update

yum install openssl openssl-devel

yum install socat

yum install epel-release

yum install conntrack-tools

Note

You may not need to install all the dependencies depending on the Kubernetes version to be installed. For more information, see Dependency Requirements.

Download KubeKey

Kubekey is the next-gen installer which provides an easy, fast and flexible way to install Kubernetes and KubeSphere.

Follow the step below to download KubeKey.

Download KubeKey from its GitHub Release Page or use the following command directly.

curl -sfL https://get-kk.kubesphere.io | VERSION=v1.0.1 sh -

Run the following command first to make sure you download KubeKey from the correct zone.

export KKZONE=cn

Run the following command to download KubeKey:

curl -sfL https://get-kk.kubesphere.io | VERSION=v1.0.1 sh -

Note

After you download KubeKey, if you transfer it to a new machine also with poor network connections to Googleapis, you must run export KKZONE=cn again before you proceed with the steps below.

Note

The commands above download the latest release (v1.0.1) of KubeKey. You can change the version number in the command to download a specific version.

Make kk executable:

chmod +x kk

Create a Multi-node Cluster

With KubeKey, you can install Kubernetes and KubeSphere together. You have the option to create a multi-node cluster by customizing parameters in the configuration file.

Create a Kubernetes cluster with KubeSphere installed (for example, --with-kubesphere v3.0.0):

./kk create config --with-kubernetes v1.17.9 --with-kubesphere v3.0.0

Note

The following Kubernetes versions have been fully tested with KubeSphere: v1.15.12, v1.16.13, v1.17.9 (default) and v1.18.6.
If you do not add the flag --with-kubesphere in the command above, KubeSphere will not be deployed unless you install it using the addons field in the configuration file or add this flag again when you use ./kk create cluster later.
If you add the flag --with-kubesphere without specifying a KubeSphere version, the latest version of KubeSphere will be installed.

A default file config-sample.yaml will be created. Modify it according to your environment.

vi config-sample.yaml

apiVersion: kubekey.kubesphere.io/v1alpha1
kind: Cluster
metadata:
  name: config-sample
spec:
  hosts:
  - {name: master1, address: 192.168.60.152, internalAddress: 192.168.60.152, user: root, password: P@ssw0rd}
  - {name: worker1, address: 192.168.60.153, internalAddress: 192.168.60.153, user: root, password: P@ssw0rd}
  - {name: worker2, address: 192.168.60.154, internalAddress: 192.168.60.154, user: root, password: P@ssw0rd}
  roleGroups:
    etcd:
    - master1
    master:
    - master1
    worker:
    - worker1
    - worker2
  controlPlaneEndpoint:
    domain: lb.kubesphere.local
    address: ""                    
    port: "6443"

Create a cluster using the configuration file you customized above:

./kk create cluster -f config-sample.yaml

Verify the installation

After the installation finishes, you can inspect the logs of installation by executing the command below:

kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=ks-install -o jsonpath='{.items[0].metadata.name}') -f

If you can see the welcome log return, it means the installation is successful.

**************************************************
#####################################################
###              Welcome to KubeSphere!           ###
#####################################################
Console: http://192.168.60.152:30880
Account: admin
Password: P@88w0rd
NOTES：
  1. After logging into the console, please check the
     monitoring status of service components in
     the "Cluster Management". If any service is not
     ready, please wait patiently until all components
     are ready.
  2. Please modify the default password after login.
#####################################################
https://kubesphere.io             20xx-xx-xx xx:xx:xx
#####################################################

Log in to the console

You will be able to use default account and password admin/P@88w0rd to log in to the console http://{$IP}:30880 to take a tour of KubeSphere. Please change the default password after login.

Enable pluggable components (Optional)

The example above demonstrates the process of a default minimal installation. To enable other components in KubeSphere, see Enable Pluggable Components for more details.

System Improvements

Update your system.
```
yum update
```

Add the required options to the kernel boot arguments:

sudo /sbin/grubby --update-kernel=ALL --args='cgroup_enable=memory cgroup.memory=nokmem swapaccount=1'

Enable the overlay2 kernel module.

echo "overlay2" | sudo tee -a /etc/modules-load.d/overlay.conf

Refresh the dynamically generated grub2 configuration.
```
sudo grub2-set-default 0
```

Adjust kernel parameters and make the change effective.

cat <<EOF | sudo tee -a /etc/sysctl.conf
vm.max_map_count = 262144
fs.may_detach_mounts = 1
net.ipv4.ip_forward = 1
vm.swappiness=1
kernel.pid_max =1000000
fs.inotify.max_user_instances=524288
EOF
sudo sysctl -p

Adjust system limits.

vim /etc/security/limits.conf
*                soft    nofile         1024000
*                hard    nofile         1024000
*                soft    memlock        unlimited
*                hard    memlock        unlimited
root             soft    nofile         1024000
root             hard    nofile         1024000
root             soft    memlock        unlimited

Remove the previous limit configuration.

sudo rm /etc/security/limits.d/20-nproc.conf

Reboot the system.
```
reboot
```

Previous : Deploy KubeSphere on VMware vSphere Next : Add New Nodes Next

What’s on this Page