Failed to deploy byconity with k8s

[Lucie-hua]

(you don't have to strictly follow this form)

Describe the issue

Step1: Deploy a k8s cluster using sealos

wget https://github.com/labring/sealos/releases/download/v4.2.0/sealos_4.2.0_linux_amd64.tar.gz
tar -zxvf sealos_4.2.0_linux_amd64.tar.gz sealos && chmod +x sealos && mv sealos /usr/bin

sealos run labring/kubernetes:v1.25.0-4.2.0 labring/helm:v3.8.2 labring/calico:v3.24.1 \
    --masters 172.26.95.56 \
    --nodes 172.26.95.57,172.26.95.59,172.26.95.58 -p xxxxxx

Step2: Deploy byconity according to https://byconity.github.io/docs/deployment/deploy-k8s

git clone https://github.com/ByConity/byconity-deploy.git
cd byconity-deploy

helm upgrade --install --create-namespace --namespace byconity -f ./examples/k8s/values.yaml byconity ./chart/byconity --set fdb.enabled=false
helm upgrade --install --create-namespace --namespace byconity -f ./examples/k8s/values.yaml byconity ./chart/byconity

some pods failed to start, and the configmap byconity-fdb-config is empty.

A clear and concise description of problems in documentation.

[wordhardqi]

@zhouwenyu392 we may improve the deployment scripts

[FourSpaces]

From the above figure, it can be seen that there are issues with the pods that require disk usage, and they are all in a pending state. I think there may not be an openebs hostpath storageClassName issue, which needs to be further examined

@Lucie-hua You can use this command: kubectl describe pod byconity-fdb-log-1 kubectl describe pod byconity-resource-manager-5f5b7d9bc8-fjzbr

[kevinthfang]

@Lucie-hua do you have further observation about his issue?