Air-gapped Installation

KubeKey is an open-source, lightweight tool for deploying Kubernetes clusters. It allows you to install Kubernetes/K3s only, both Kubernetes/K3s and KubeSphere, and other cloud-native plugins in a flexible, fast, and convenient way. Additionally, it is an effective tool for scaling and upgrading clusters.

In KubeKey v2.1.0, we bring in concepts of manifest and artifact, which provides a solution for air-gapped installation of Kubernetes clusters. A manifest file describes information of the current Kubernetes cluster and defines content in an artifact. Previously, users had to prepare deployment tools, image (.tar) file, and other binaries as the Kubernetes version and image to deploy are different. Now, with KubeKey, air-gapped installation can never be so easy. You simply use a manifest file to define what you need for your cluster in air-gapped environments, and then export the artifact file to quickly and easily deploy image registries and Kubernetes cluster.

Prerequisites

Host IPHost NameUsage
192.168.0.2node1Online host for packaging the source cluster
192.168.0.3node2Control plane node of the air-gapped environment
192.168.0.4node3Image registry node of the air-gapped environment

Preparations

  1. Run the following commands to download KubeKey.

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

    1. curl -sfL https://get-kk.kubesphere.io | VERSION=v3.0.7 sh -

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

    1. export KKZONE=cn

    Run the following command to download KubeKey:

    1. curl -sfL https://get-kk.kubesphere.io | VERSION=v3.0.7 sh -

  2. On the online host, run the following command and copy content in the manifest-example.

    1. vim manifest.yaml
    1. ---
    2. apiVersion: kubekey.kubesphere.io/v1alpha2
    3. kind: Manifest
    4. metadata:
    5.   name: sample
    6. spec:
    7.   arches:
    8.   - amd64
    9.   operatingSystems:
    10.   - arch: amd64
    11.     type: linux
    12.     id: centos
    13.     version: "7"
    14.     repository:
    15.       iso:
    16.         localPath:
    17.         url: https://github.com/kubesphere/kubekey/releases/download/v3.0.7/centos7-rpms-amd64.iso
    18.   - arch: amd64
    19.     type: linux
    20.     id: ubuntu
    21.     version: "20.04"
    22.     repository:
    23.       iso:
    24.         localPath:
    25.         url: https://github.com/kubesphere/kubekey/releases/download/v3.0.7/ubuntu-20.04-debs-amd64.iso
    26.   kubernetesDistributions:
    27.   - type: kubernetes
    28.     version: v1.22.12
    29.   components:
    30.     helm:
    31.       version: v3.9.0
    32.     cni:
    33.       version: v0.9.1
    34.     etcd:
    35.       version: v3.4.13
    36.    ## For now, if your cluster container runtime is containerd, KubeKey will add a docker 20.10.8 container runtime in the below list.
    37.    ## The reason is KubeKey creates a cluster with containerd by installing a docker first and making kubelet connect the socket file of containerd which docker contained.
    38.     containerRuntimes:
    39.     - type: docker
    40.       version: 20.10.8
    41.     crictl:
    42.       version: v1.24.0
    43.     docker-registry:
    44.       version: "2"
    45.     harbor:
    46.       version: v2.5.3
    47.     docker-compose:
    48.       version: v2.2.2
    49.   images:
    50.   - docker.io/kubesphere/kube-apiserver:v1.22.12
    51.   - docker.io/kubesphere/kube-controller-manager:v1.22.12
    52.   - docker.io/kubesphere/kube-proxy:v1.22.12
    53.   - docker.io/kubesphere/kube-scheduler:v1.22.12
    54.   - docker.io/kubesphere/pause:3.5
    55.   - docker.io/coredns/coredns:1.8.0
    56.   - docker.io/calico/cni:v3.23.2
    57.   - docker.io/calico/kube-controllers:v3.23.2
    58.   - docker.io/calico/node:v3.23.2
    59.   - docker.io/calico/pod2daemon-flexvol:v3.23.2
    60.   - docker.io/calico/typha:v3.23.2
    61.   - docker.io/kubesphere/flannel:v0.12.0
    62.   - docker.io/openebs/provisioner-localpv:3.4.0
    63.   - docker.io/openebs/linux-utils:3.4.0
    64.   - docker.io/library/haproxy:2.3
    65.   - docker.io/kubesphere/nfs-subdir-external-provisioner:v4.0.2
    66.   - docker.io/kubesphere/k8s-dns-node-cache:1.15.12
    67.   - docker.io/kubesphere/ks-installer:v3.4.0
    68.   - docker.io/kubesphere/ks-apiserver:v3.4.0
    69.   - docker.io/kubesphere/ks-console:v3.4.0
    70.   - docker.io/kubesphere/ks-controller-manager:v3.4.0
    71.   - docker.io/kubesphere/ks-upgrade:v3.4.0
    72.   - docker.io/kubesphere/kubectl:v1.22.0
    73.   - docker.io/kubesphere/kubectl:v1.21.0
    74.   - docker.io/kubesphere/kubectl:v1.20.0
    75.   - docker.io/kubesphere/kubefed:v0.8.1
    76.   - docker.io/kubesphere/tower:v0.2.0
    77.   - docker.io/minio/minio:RELEASE.2019-08-07T01-59-21Z
    78.   - docker.io/minio/mc:RELEASE.2019-08-07T23-14-43Z
    79.   - docker.io/csiplugin/snapshot-controller:v4.0.0
    80.   - docker.io/kubesphere/nginx-ingress-controller:v1.1.0
    81.   - docker.io/mirrorgooglecontainers/defaultbackend-amd64:1.4
    82.   - docker.io/kubesphere/metrics-server:v0.4.2
    83.   - docker.io/library/redis:5.0.14-alpine
    84.   - docker.io/library/haproxy:2.0.25-alpine
    85.   - docker.io/library/alpine:3.14
    86.   - docker.io/osixia/openldap:1.3.0
    87.   - docker.io/kubesphere/netshoot:v1.0
    88.   - docker.io/kubeedge/cloudcore:v1.9.2
    89.   - docker.io/kubeedge/iptables-manager:v1.9.2
    90.   - docker.io/kubesphere/edgeservice:v0.2.0
    91.   - docker.io/openpolicyagent/gatekeeper:v3.5.2
    92.   - docker.io/kubesphere/openpitrix-jobs:v3.4.0
    93.   - docker.io/kubesphere/devops-apiserver:ks-v3.4.0
    94.   - docker.io/kubesphere/devops-controller:ks-v3.4.0
    95.   - docker.io/kubesphere/devops-tools:ks-v3.4.0
    96.   - docker.io/kubesphere/ks-jenkins:v3.4.0-2.319.1
    97.   - docker.io/jenkins/inbound-agent:4.10-2
    98.   - docker.io/kubesphere/builder-base:v3.2.2
    99.   - docker.io/kubesphere/builder-nodejs:v3.2.0
    100.   - docker.io/kubesphere/builder-maven:v3.2.0
    101.   - docker.io/kubesphere/builder-maven:v3.2.1-jdk11
    102.   - docker.io/kubesphere/builder-python:v3.2.0
    103.   - docker.io/kubesphere/builder-go:v3.2.0
    104.   - docker.io/kubesphere/builder-go:v3.2.2-1.16
    105.   - docker.io/kubesphere/builder-go:v3.2.2-1.17
    106.   - docker.io/kubesphere/builder-go:v3.2.2-1.18
    107.   - docker.io/kubesphere/builder-base:v3.2.2-podman
    108.   - docker.io/kubesphere/builder-nodejs:v3.2.0-podman
    109.   - docker.io/kubesphere/builder-maven:v3.2.0-podman
    110.   - docker.io/kubesphere/builder-maven:v3.2.1-jdk11-podman
    111.   - docker.io/kubesphere/builder-python:v3.2.0-podman
    112.   - docker.io/kubesphere/builder-go:v3.2.0-podman
    113.   - docker.io/kubesphere/builder-go:v3.2.2-1.16-podman
    114.   - docker.io/kubesphere/builder-go:v3.2.2-1.17-podman
    115.   - docker.io/kubesphere/builder-go:v3.2.2-1.18-podman
    116.   - docker.io/kubesphere/s2ioperator:v3.2.1
    117.   - docker.io/kubesphere/s2irun:v3.2.0
    118.   - docker.io/kubesphere/s2i-binary:v3.2.0
    119.   - docker.io/kubesphere/tomcat85-java11-centos7:v3.2.0
    120.   - docker.io/kubesphere/tomcat85-java11-runtime:v3.2.0
    121.   - docker.io/kubesphere/tomcat85-java8-centos7:v3.2.0
    122.   - docker.io/kubesphere/tomcat85-java8-runtime:v3.2.0
    123.   - docker.io/kubesphere/java-11-centos7:v3.2.0
    124.   - docker.io/kubesphere/java-8-centos7:v3.2.0
    125.   - docker.io/kubesphere/java-8-runtime:v3.2.0
    126.   - docker.io/kubesphere/java-11-runtime:v3.2.0
    127.   - docker.io/kubesphere/nodejs-8-centos7:v3.2.0
    128.   - docker.io/kubesphere/nodejs-6-centos7:v3.2.0
    129.   - docker.io/kubesphere/nodejs-4-centos7:v3.2.0
    130.   - docker.io/kubesphere/python-36-centos7:v3.2.0
    131.   - docker.io/kubesphere/python-35-centos7:v3.2.0
    132.   - docker.io/kubesphere/python-34-centos7:v3.2.0
    133.   - docker.io/kubesphere/python-27-centos7:v3.2.0
    134.   - quay.io/argoproj/argocd:v2.3.3
    135.   - quay.io/argoproj/argocd-applicationset:v0.4.1
    136.   - ghcr.io/dexidp/dex:v2.30.2
    137.   - docker.io/library/redis:6.2.6-alpine
    138.   - docker.io/jimmidyson/configmap-reload:v0.5.0
    139.   - docker.io/prom/prometheus:v2.34.0
    140.   - docker.io/kubesphere/prometheus-config-reloader:v0.55.1
    141.   - docker.io/kubesphere/prometheus-operator:v0.55.1
    142.   - docker.io/kubesphere/kube-rbac-proxy:v0.11.0
    143.   - docker.io/kubesphere/kube-state-metrics:v2.5.0
    144.   - docker.io/prom/node-exporter:v1.3.1
    145.   - docker.io/prom/alertmanager:v0.23.0
    146.   - docker.io/thanosio/thanos:v0.25.2
    147.   - docker.io/grafana/grafana:8.3.3
    148.   - docker.io/kubesphere/kube-rbac-proxy:v0.8.0
    149.   - docker.io/kubesphere/notification-manager-operator:v1.4.0
    150.   - docker.io/kubesphere/notification-manager:v1.4.0
    151.   - docker.io/kubesphere/notification-tenant-sidecar:v3.2.0
    152.   - docker.io/kubesphere/elasticsearch-curator:v5.7.6
    153.   - docker.io/kubesphere/elasticsearch-oss:6.8.22
    154.   - docker.io/kubesphere/fluentbit-operator:v0.13.0
    155.   - docker.io/library/docker:19.03
    156.   - docker.io/kubesphere/fluent-bit:v1.8.11
    157.   - docker.io/kubesphere/log-sidecar-injector:1.1
    158.   - docker.io/elastic/filebeat:6.7.0
    159.   - docker.io/kubesphere/kube-events-operator:v0.4.0
    160.   - docker.io/kubesphere/kube-events-exporter:v0.4.0
    161.   - docker.io/kubesphere/kube-events-ruler:v0.4.0
    162.   - docker.io/kubesphere/kube-auditing-operator:v0.2.0
    163.   - docker.io/kubesphere/kube-auditing-webhook:v0.2.0
    164.   - docker.io/istio/pilot:1.11.1
    165.   - docker.io/istio/proxyv2:1.11.1
    166.   - docker.io/jaegertracing/jaeger-operator:1.27
    167.   - docker.io/jaegertracing/jaeger-agent:1.27
    168.   - docker.io/jaegertracing/jaeger-collector:1.27
    169.   - docker.io/jaegertracing/jaeger-query:1.27
    170.   - docker.io/jaegertracing/jaeger-es-index-cleaner:1.27
    171.   - docker.io/kubesphere/kiali-operator:v1.38.1
    172.   - docker.io/kubesphere/kiali:v1.38
    173.   - docker.io/library/busybox:1.31.1
    174.   - docker.io/library/nginx:1.14-alpine
    175.   - docker.io/joosthofman/wget:1.0
    176.   - docker.io/nginxdemos/hello:plain-text
    177.   - docker.io/library/wordpress:4.8-apache
    178.   - docker.io/mirrorgooglecontainers/hpa-example:latest
    179.   - docker.io/fluent/fluentd:v1.4.2-2.0
    180.   - docker.io/library/perl:latest
    181.   - docker.io/kubesphere/examples-bookinfo-productpage-v1:1.16.2
    182.   - docker.io/kubesphere/examples-bookinfo-reviews-v1:1.16.2
    183.   - docker.io/kubesphere/examples-bookinfo-reviews-v2:1.16.2
    184.   - docker.io/kubesphere/examples-bookinfo-details-v1:1.16.2
    185.   - docker.io/kubesphere/examples-bookinfo-ratings-v1:1.16.3
    186.   - docker.io/weaveworks/scope:1.13.0

    Note

    • If the artifact file to export contains ISO dependencies, such as conntarck and chrony, set the IP address for downloading the ISO dependencies in .repostiory.iso.url of operationSystem. Alternatively, you can download the ISO package in advance and fill in the local path in localPath and delete the url configuration item.

    • You need to enable harbor and docker-compose configuration items, which will be used when you use KubeKey to build a Harbor registry for pushing images.

    • By default, the list of images in the created manifest is obtained from docker.io.

    • You can customize the manifest-sample.yaml file to export the desired artifact file.

    • You can download the ISO files at https://github.com/kubesphere/kubekey/releases/tag/v3.0.7.

  3. If you already deployed a cluster, you can run the following command in the cluster to create a manifest file and configure the file according to the sample in Step 2.

    1. ./kk create manifest

  4. Export the artifact.

    Run the following command directly:

    1. ./kk artifact export -m manifest-sample.yaml -o kubesphere.tar.gz

    Run the following commands:

    1. export KKZONE=cn
    3. ./kk artifact export -m manifest-sample.yaml -o kubesphere.tar.gz

    Note

    An artifact is a .tgz package containing the image package (.tar) and associated binaries exported from the specified manifest file. You can specify an artifact in the KubeKey commands for initializing the image registry, creating clusters, adding nodes, and upgrading clusters, and then KubeKey will automatically unpack the artifact and use the unpacked file when running the command.

    • Make sure the network connection is working.

    • KubeKey will resolve image names in the image list. If the image registry requires authentication, you can configure it in .registry.auths in the manifest file.

Install Clusters in the Air-gapped Environment

  1. Copy the downloaded KubeKey and artifact to nodes in the air-gapped environment using a USB device.

  2. Run the following command to create a configuration file for the air-gapped cluster:

    1. ./kk create config --with-kubesphere v3.4.0 --with-kubernetes v1.22.12 -f config-sample.yaml

  3. Run the following command to modify the configuration file:

    1. vim config-sample.yaml

    Note

    • Modify the node information according to the actual configuration of the air-gapped environment.
    • You must specify the node where the registry to deploy (for KubeKey deployment of self-built Harbor registries).
    • In registry, the value of type must be specified as that of harbor. Otherwise, the docker registry is installed by default.
    1. apiVersion: kubekey.kubesphere.io/v1alpha2
    2. kind: Cluster
    3. metadata:
    4.   name: sample
    5. spec:
    6.   hosts:
    7.   - {name: master, address: 192.168.0.3, internalAddress: 192.168.0.3, user: root, password: "<REPLACE_WITH_YOUR_ACTUAL_PASSWORD>"}
    8.   - {name: node1, address: 192.168.0.4, internalAddress: 192.168.0.4, user: root, password: "<REPLACE_WITH_YOUR_ACTUAL_PASSWORD>"}
    10.   roleGroups:
    11.     etcd:
    12.     - master
    13.     control-plane:
    14.     - master
    15.     worker:
    16.     - node1
    17.     # If you want to use KubeKey to automatically deploy the image registry, set this value. You are advised to separately deploy the registry and the cluster.
    18.     registry:
    19.     - node1
    20.   controlPlaneEndpoint:
    21.     ## Internal loadbalancer for apiservers
    22.     # internalLoadbalancer: haproxy
    24.     domain: lb.kubesphere.local
    25.     address: ""
    26.     port: 6443
    27.   kubernetes:
    28.     version: v1.22.12
    29.     clusterName: cluster.local
    30.   network:
    31.     plugin: calico
    32.     kubePodsCIDR: 10.233.64.0/18
    33.     kubeServiceCIDR: 10.233.0.0/18
    34.     ## multus support. https://github.com/k8snetworkplumbingwg/multus-cni
    35.     multusCNI:
    36.       enabled: false
    37.   registry:
    38.     # To use KubeKey to deploy Harbor, set the value of this parameter to harbor. If you do not set this parameter and still use KubeKey to create an container image registry, the docker registry is used by default.
    39.     type: harbor
    40.     # If Harbor or other registries deployed by using KubeKey requires login, you can set the auths parameter of the registry. However, if you create a docker registry using KubeKey, you do not need to set the auths parameter.
    41.     # Note: If you use KubeKey to deploy Harbor, do not set this parameter until Harbor is started.
    42.     #auths:
    43.     #  "dockerhub.kubekey.local":
    44.     #    username: admin
    45.     #    password: Harbor12345
    46.     # Set the private registry to use during cluster deployment.
    47.     privateRegistry: ""
    48.     namespaceOverride: ""
    49.     registryMirrors: []
    50.     insecureRegistries: []
    51.   addons: []

  4. Run the following command to install an image registry:

    1. ./kk init registry -f config-sample.yaml -a kubesphere.tar.gz

    Note

    The parameters in the command are explained as follows:

    • config-sample.yaml: Specifies the configuration file of the cluster in the air-gapped environment.

    • kubesphere.tar.gz: Specifies the image package of the source cluster.

  5. Create a Harbor project.

    Note

    As Harbor adopts the Role-based Access Control (RBAC) mechanism, which means that only specified users can perform certain operations. Therefore, you must create a project before pushing images to Harbor. Harbor supports two types of projects:

    • Public: All users can pull images from the project.

    • Private: Only project members can pull images from the project.

    The username and password for logging in to Harbor is admin and Harbor12345 by default. The installation file of Harbor is located in /opt/harbor, where you can perform O&M of Harbor.

    Method 1: Run the following commands to create a Harbor project.

    a. Run the following command to download the specified script to initialize the Harbor registry:

    1. curl -O https://raw.githubusercontent.com/kubesphere/ks-installer/master/scripts/create_project_harbor.sh

    b. Run the following command to modify the script configuration file:

    1. vim create_project_harbor.sh
    1. #!/usr/bin/env bash
    3. # Copyright 2018 The KubeSphere Authors.
    4. #
    5. # Licensed under the Apache License, Version 2.0 (the "License");
    6. # you may not use this file except in compliance with the License.
    7. # You may obtain a copy of the License at
    8. #
    9. #     http://www.apache.org/licenses/LICENSE-2.0
    10. #
    11. # Unless required by applicable law or agreed to in writing, software
    12. # distributed under the License is distributed on an "AS IS" BASIS,
    13. # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    14. # See the License for the specific language governing permissions and
    15. # limitations under the License.
    17. url="https://dockerhub.kubekey.local"  #Change the value of url to https://dockerhub.kubekey.local.
    18. user="admin"
    19. passwd="Harbor12345"
    21. harbor_projects=(library
    22.     kubesphereio
    23.     kubesphere
    24.     calico
    25.     coredns
    26.     openebs
    27.     csiplugin
    28.     minio
    29.     mirrorgooglecontainers
    30.     osixia
    31.     prom
    32.     thanosio
    33.     jimmidyson
    34.     grafana
    35.     elastic
    36.     istio
    37.     jaegertracing
    38.     jenkins
    39.     weaveworks
    40.     openpitrix
    41.     joosthofman
    42.     nginxdemos
    43.     fluent
    44.     kubeedge
    45. )
    47. for project in "${harbor_projects[@]}"; do
    48.     echo "creating $project"
    49.     curl -u "${user}:${passwd}" -X POST -H "Content-Type: application/json" "${url}/api/v2.0/projects" -d "{ \"project_name\": \"${project}\", \"public\": true}" -k #Add -k at the end of the curl command.
    50. done

    Note

    • Change the value of url to https://dockerhub.kubekey.local.

    • The project name of the registry must be the same as that of the image list.

    • Add -k at the end of the curl command.

    c. Run the following commands to create a Harbor project:

    1. chmod +x create_project_harbor.sh
    1. ./create_project_harbor.sh

    Method 2: Log in to Harbor and create a project. Set the project to Public, so that any user can pull images from this project. For more information, please refer to Create Projects.

    harbor-login

  6. Run the following command again to modify the cluster configuration file：

    1. vim config-sample.yaml

    Note

    • In auths, add dockerhub.kubekey.local and the username and password.
    • In privateRegistry, add dockerhub.kubekey.local.
    1.   ...
    2.   registry:
    3.     type: harbor
    4.     auths:
    5.       "dockerhub.kubekey.local":
    6.         username: admin
    7.         password: Harbor12345
    8.     privateRegistry: "dockerhub.kubekey.local"
    9.     namespaceOverride: "kubesphereio"
    10.     registryMirrors: []
    11.     insecureRegistries: []
    12.   addons: []

    Note

    • In auths, enter dockerhub.kubekey.local, username (admin) and password (Harbor12345).
    • In privateRegistry, enter dockerhub.kubekey.local.
    • In namespaceOverride, enter kubesphereio.

  7. Run the following command to install a KubeSphere cluster:

    1. ./kk create cluster -f config-sample1.yaml -a kubesphere.tar.gz --with-packages

    The parameters are explained as follows：

    • config-sample.yaml: Specifies the configuration file for the cluster in the air-gapped environment.
    • kubesphere.tar.gz: Specifies the tarball image from which the source cluster is packaged.
    • --with-packages: This parameter is required if you want to install the ISO dependencies.

  8. Run the following command to view the cluster status:

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

    After the installation is completed, the following information is displayed:

    1. **************************************************
    2. #####################################################
    3. ###              Welcome to KubeSphere!           ###
    4. #####################################################
    6. Console: http://192.168.0.3:30880
    7. Account: admin
    8. Password: P@88w0rd
    10. NOTES：
    11. 1. After you log into the console, please check the
    12. monitoring status of service components in
    13. the "Cluster Management". If any service is not
    14. ready, please wait patiently until all components
    15. are up and running.
    16. 1. Please change the default password after login.
    18. #####################################################
    19. https://kubesphere.io             2022-02-28 23:30:06
    20. #####################################################

  9. Access KubeSphere’s web console at http://{IP}:30880 using the default account and password admin/P@88w0rd.

login

Note

To access the console, make sure that port 30880 is enabled in your security group.

Feedback

Was this page Helpful?

Yes No