Single-Node Deployment
The single-node mode means that KubeSphere is deployed on a single node. This mode is prepared for users who are new to KubeSphere and need to quickly get started with it. Single-node deployment helps you quickly deploy KubeSphere and Kubernetes with zero configuration.
- Install the dependencies.
yum install -y curl socat conntrack openssl ipset ipvsadm
- Download the installation tool KubeKey.
- Method 1: Use the script to obtain KubeKey.
cd /home curl -sfL https://get-kk.kubesphere.io | VERSION=v3.0.13 sh -
- Method 2: Download the KubeKey executable file package and upload it to the /home directory. Decompress the package and use it directly.
Download link: https://kubernetes.pek3b.qingstor.com/kubekey/releases/download/v3.0.13/kubekey-v3.0.13-linux-arm64.tar.gz
- Method 1: Use the script to obtain KubeKey.
- Pre-download the container image package.
The defaultbackend container image pulled by default does not support the Arm architecture. To ensure that the container can run properly on the Arm architecture, pull the container image package that supports the Arm architecture to the local host and replace the default image tag for it. The operation is as follows:
docker pull mirrorgooglecontainers/defaultbackend-arm64:1.4 docker tag mirrorgooglecontainers/defaultbackend-arm64:1.4 mirrorgooglecontainers/defaultbackend-amd64:1.4
- In other scenarios, if the pulled image does not support the Arm architecture, you can refer to this step to pull the container image package that supports the Arm architecture to the local host and replace its image tag with the default image tag. This operation can solve the image compatibility problem.
Run the following command to modify the container image tag:
docker tag SOURCE_IMAGE:TAG1 TARGET_IMAGE:TAG2
SOURCE_IMAGE:TAG1 indicates the tag before modification, and TARGET_IMAGE:TAG2 indicates the tag after modification.
- If you cannot pull images from dockerhub.io, you are advised to configure the Docker image accelerator in advance and use other image sources to download the required Docker images. For details about how to change the image source, see Changing the Image Source.
- In other scenarios, if the pulled image does not support the Arm architecture, you can refer to this step to pull the container image package that supports the Arm architecture to the local host and replace its image tag with the default image tag. This operation can solve the image compatibility problem.
- Install Kubernetes and KubeSphere at the same time.
Kubernetes v1.23.10 and KubeSphere v3.4.1 are used as examples:
cd /home ./kk create cluster --with-kubernetes v1.23.10 --with-kubesphere v3.4.1
- The --with-kubernetes version parameter specifies the Kubernetes version to be installed. (For details about the supported Kubernetes versions, see https://github.com/kubesphere/kubekey/blob/master/README.md.) If --with-kubernetes is not added or version is not specified, v1.23.10 is installed by default.
- The --with-kubesphere version parameter specifies the KubeSphere version to be installed. If --with-kubesphere is not added, KubeSphere is not installed. If version is not specified, the latest KubeSphere is installed by default.
After the command in this step is executed, KubeKey checks the installation environment. The check result is displayed in a table and the prompt information "Continue this installation? [yes/no]:" is displayed. Check whether all dependency requirements are met, type yes, and press Enter.
During the installation, related component packages are downloaded from the Internet.
After the installation is complete, the IP address and port number of the web console are displayed in the command output. The default port number is 30880. Now, you can use the default user name admin and password P@88w0rd to access the KubeSphere web console through <NodeIP>:30880 (http://192.168.1.102:30880 is used in this example).