Common Problems and Solutions for Interconnecting with the Tanzu Kubernetes Cluster on Huawei

A Pod Cannot Be Created Because the PSP Permission Is Not Created

Mon, 01 Jan 0001 00:00:00 +0000

Symptom

When huawei-csi-controller and huawei-csi-node are created, only the Deployment and DaemonSet resources are successfully created, and no Pod is created for the controller and node.

Root Cause Analysis

The service account used for creating resources does not have the “use” permission of the PSP policy.

Solution or Workaround

Use a remote access tool, such as PuTTY, to log in to any master node in the Kubernetes cluster through the management IP address.

Changing the Mount Point of a Host

Mon, 01 Jan 0001 00:00:00 +0000

Symptom

A Pod fails to be created, and error message “mount point does not exist” is recorded in Huawei CSI logs.

Root Cause Analysis

The native Kubernetes cluster in the pods-dir directory of huawei-csi-node is inconsistent with the Tanzu Kubernetes cluster.

Solution or Workaround

Go to the helm/esdk/ directory and run the vi values.yaml command to open the configuration file.
```
vi values.yaml
```
Change the value of kubeletConfigDir to the actual installation directory of kubelet.

Changing the Default Port of the livenessprobe Container

Mon, 01 Jan 0001 00:00:00 +0000

Symptom

The livenessprobe container of the huawei-csi-controller component keeps restarting.

Root Cause Analysis

The default port (9808) of the livenessprobe container of huawei-csi-controller conflicts with the existing vSphere CSI port of Tanzu.

Solution or Workaround

Change the default port of the livenessprobe container to an idle port.

Go to the helm/esdk directory and run the vi values.yaml command to open the configuration file.
```
vi values.yaml
```
Change the default value 9808 of controller.livenessProbePort to an idle port, for example, 9809.

Failed to Create an Ephemeral Volume

Mon, 01 Jan 0001 00:00:00 +0000

Symptom

A generic ephemeral volume fails to be created, and the error message PodSecurityPolicy: unable to admit pod: [spec.volumes[0]: Invalid value: “ephemeral”: ephemeral volumes are not allowed to be used spec.volumes[0] is displayed.

Root Cause Analysis

The current PSP policy does not contain the permission to use ephemeral volumes.

Solution or Workaround

Add the permission to use ephemeral volumes to the default PSP pks-privileged and pks-restricted. The following is an example of modifying pks-privileged: