Documentation
Rate This Document
Findability
Accuracy
Completeness
Readability
SubmitClose

KubeSphere Installation Stuck in Waiting for the Installation to Complete

Symptom

During the KubeSphere installation, the progress is stuck at waiting for the KubeSphere installation to be complete. The following information is displayed:

Key Process and Cause Analysis

When you are waiting for the installation to complete, the containers are started to download the container images required by related services. Due to factors such as network problems, the container images fail to be downloaded. As a result, the containers of the related services continuously attempt to be redeployed.

Run the following command to check whether all pods are successfully created:

kubectl get pod -A

If ImagePullBackOff is displayed in the STATUS column, the container image fails to be downloaded.

Run the following command to query the logs of the faulty container for more details:

kubectl -n NAMESPACE describe pod NAME
  • NAMESPACE indicates the container name in the NAMESPACE column obtained by running the kubectl get pod -A command.
  • NAME indicates the container name in the NAME column obtained by running the kubectl get pod -A command.

As shown in the following figure, the query log shows that the container image k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.4.0 fails to be downloaded.

Conclusion and Solution

Run the commands to manually pull the container image or pull the container image from another host where the image is available and upload it to the installation environment. The container will be automatically redeployed using the existing local image.

Note that the container image tag must be the same as that displayed in the error log.

k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.4.0 is used as an example. The procedure is as follows:

  1. Manually pull the container image.
    docker pull k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.4.0 --platform arm64
  2. Export the container image.
    docker save -o csi-node-driver-registrar.tar k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.4.0
  3. Import the local container image.
    docker load -i csi-node-driver-registrar.tar
  4. Modify the container image tag.
    docker tag k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.4.0 dockerregist/sig-storage/csi-node-driver-registrar:v2.4.1
Parent topic: Troubleshooting