Пытаюсь развернуть rocketchat helm upgrade --install --namespace rocketchat --create-namespace --set host=rocketchat.example.com

--set ingress.enabled=true --set mongodb.auth.password=$(echo -n $(openssl rand -base64 32)),mongodb.auth.rootPassword=$(echo -n $(openssl rand -base64 32)) --set persistence.enabled=true --set persistence.storageClass=fast.ru-3a --set mongodb.persistence.storageClass=fast.ru-3a rocketchat rocketchat/rocketchat

но поды не стартуют
kubectl get pods -n rocketchat
NAME READY STATUS RESTARTS AGE
rocketchat-mongodb-0 0/1 Pending 0 12m
rocketchat-rocketchat-788564bc7c-hv4w7 0/1 CrashLoopBackOff 6 (18s ago) 12m

9m46s Normal Pulled pod/rocketchat-rocketchat-788564bc7c-hv4w7 Container image "registry.rocket.chat/rocketchat/rocket.chat:4.6.1" already present on machine
9m45s Normal Created pod/rocketchat-rocketchat-788564bc7c-hv4w7 Created container rocketchat
9m45s Normal Started pod/rocketchat-rocketchat-788564bc7c-hv4w7 Started container rocketchat
8m59s Warning Unhealthy pod/rocketchat-rocketchat-788564bc7c-hv4w7 Readiness probe failed: Get "http://10.10.215.35:3000/api/info": dial tcp 10.10.215.35:3000: connect: connection refused
4m12s Normal FailedBinding persistentvolumeclaim/datadir-rocketchat-mongodb-0 no persistent volumes available for this claim and no storage class is set
2m56s Normal NotTriggerScaleUp pod/rocketchat-mongodb-0 pod didn't trigger scale-up:
2m14s Warning BackOff pod/rocketchat-rocketchat-788564bc7c-hv4w7 Back-off restarting failed container
22s Warning FailedScheduling pod/rocketchat-mongodb-0 0/2 nodes are available: 2 pod has unbound immediate PersistentVolumeClaims.

kubectl get pv -A
NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE
pvc-597c3c34-3f80-4d0c-93eb-6af08c418b41 8Gi RWO Delete Bound rocketchat/rocketchat-rocketchat fast.ru-3a 13m

kubectl get pvc -A
NAMESPACE NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
rocketchat datadir-rocketchat-mongodb-0 Pending 99m
rocketchat rocketchat-rocketchat Bound pvc-597c3c34-3f80-4d0c-93eb-6af08c418b41 8Gi RWO fast.ru-3a 13m

подскажите, что я упускаю и как все таки запустить рокетчат?

Tl;dr

27s Warning FailedScheduling pod/rocketchat-mongodb-0 0/2 nodes are available: 2 pod has unbound immediate PersistentVolumeClaims.

у тебя хранилища в кластере нет

так вроде бы создается kubectl get pv -A NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE pvc-597c3c34-3f80-4d0c-93eb-6af08c418b41 8Gi RWO Delete Bound rocketchat/rocketchat-rocketchat fast.ru-3a 13m kubectl get pvc -A NAMESPACE NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE rocketchat datadir-rocketchat-mongodb-0 Pending 99m rocketchat rocketchat-rocketchat Bound pvc-597c3c34-3f80-4d0c-93eb-6af08c418b41 8Gi RWO fast.ru-3a 13m

так он в пендинге

пересоздал kubectl get pv -A NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE pvc-7c5f9bbf-fef1-40dd-ae97-f25de4ac9b50 8Gi RWO Delete Bound rocketchat/rocketchat-rocketchat fast.ru-3a 2m9s pvc-f4e729d9-c125-4724-8b36-2af8bad8ef24 8Gi RWO Delete Bound rocketchat/datadir-rocketchat-mongodb-0 fast.ru-3a 2m9s kubectl get pvc -A NAMESPACE NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE rocketchat datadir-rocketchat-mongodb-0 Bound pvc-f4e729d9-c125-4724-8b36-2af8bad8ef24 8Gi RWO fast.ru-3a 2m16s rocketchat rocketchat-rocketchat Bound pvc-7c5f9bbf-fef1-40dd-ae97-f25de4ac9b50 8Gi RWO fast.ru-3a 2m16s

Ну все хорошо

да, но kubectl get pods -n rocketchat NAME READY STATUS RESTARTS AGE rocketchat-mongodb-0 0/1 Init:0/1 0 115s rocketchat-rocketchat-7455f689dd-7ptq5 0/1 CrashLoopBackOff 2 (12s ago) 4m27s 92s Warning FailedMount pod/rocketchat-mongodb-0 Unable to attach or mount volumes: unmounted volumes=[datadir], unattached volumes=[datadir kube-api-access-lzl2t scripts]: timed out waiting for the condition 90s Normal NotTriggerScaleUp pod/rocketchat-rocketchat-7455f689dd-m6pxz pod didn't trigger scale-up: 29s Warning FailedScheduling pod/rocketchat-rocketchat-7455f689dd-m6pxz 0/2 nodes are available: 2 node(s) had taint {node.kubernetes.io/disk-pressure: }, that the pod didn't tolerate.

Судя по сторажклассам предполагаю что у тебя там Selectel да?