Failed to Start the http-backupend Service During KubeSphere Installation

Symptom

During the KubeSphere installation, the http-backupend service fails to be started.

Key Process and Cause Analysis

The cause is that the container image package in use does not support the Arm architecture. Replace it with a container image that supports the Arm architecture to solve the problem.

Conclusion and Solution

To replace the container image package with one that supports the Arm architecture, perform the following steps:

1. On the node where the exception occurs, obtain the container image that supports the Arm architecture (that is, obtain the same-version container image that supports the Arm architecture from the third party).

   docker pull mirrorgooglecontainers/defaultbackend-arm64:1.4

   To ensure the consistent name style of the container images, run the following command to tag the container image again:

   docker tag docker.io/mirrorgooglecontainers/defaultbackend-arm64:1.4 registry.cn-beijing.aliyuncs.com/kubesphereio/defaultbackend-arm64:1.4

2. On the management node, modify the container image used for deployment:

   kubectl set image deployment/default-http-backend default-http-backend=registry.cn-beijing.aliyuncs.com/kubesphereio/defaultbackend-arm64:1.4 -n kubesphere-controls-system

   After the execution is complete, the http-backupend service is re-created.

3. Run the following command to check the creation status of the http-backupend service:

   kubectl get pod -A|grep "http-backend"

   As displayed in the command output, the new http-backupend service is being created.

   

   After a short while, run the kubectl get pod -A|grep "http-backend" command again to check the status. In the command output, the status of the http-backupend service is Running.