Это значит не работает?

пытается запуститься, ждём

А раньше такого не было

Посмотри через describe pod - чего он ждет

MacBook-Pro-Komil:helm mirjon$ kubectl describe pod chroma-dev-chromadb-0 Name: chroma-dev-chromadb-0 Namespace: default Priority: 0 Service Account: default Node: <none> Labels: app.kubernetes.io/instance=chroma-dev app.kubernetes.io/managed-by=Helm app.kubernetes.io/name=chromadb app.kubernetes.io/version=0.4.9 controller-revision-hash=chroma-dev-chromadb-7c56794fdb helm.sh/chart=chromadb-0.1.15 statefulset.kubernetes.io/pod-name=chroma-dev-chromadb-0 Annotations: <none> Status: Pending IP: IPs: <none> Controlled By: StatefulSet/chroma-dev-chromadb Containers: chromadb: Image: ghcr.io/amikos-tech/chromadb-chart/chroma:0.4.9 Port: 8000/TCP Host Port: 0/TCP Liveness: tcp-socket :8000 delay=0s timeout=10s period=5s #success=1 #failure=40 Readiness: tcp-socket :8000 delay=0s timeout=10s period=5s #success=1 #failure=20 Startup: tcp-socket :8000 delay=10s timeout=1s period=5s #success=1 #failure=1000 Environment: POD_NAME: chroma-dev-chromadb-0 (v1:metadata.name) IS_PERSISTENT: true PERSIST_DIRECTORY: /index_data ALLOW_RESET: false ANONYMIZED_TELEMETRY: false CHROMA_SERVER_CORS_ALLOW_ORIGINS: ["*"] CHROMA_API_IMPL: chromadb.api.segment.SegmentAPI CHROMA_SERVER_HOST: 0.0.0.0 CHROMA_SERVER_HTTP_PORT: 8000 CHROMA_SERVER_AUTH_CREDENTIALS: <set to the key 'token' in secret 'chromadb-auth'> Optional: false CHROMA_SERVER_AUTH_CREDENTIALS_PROVIDER: chromadb.auth.token.TokenConfigServerAuthCredentialsProvider CHROMA_SERVER_AUTH_PROVIDER: chromadb.auth.token.TokenAuthServerProvider CHROMA_SERVER_AUTH_TOKEN_TRANSPORT_HEADER: AUTHORIZATION Mounts: /chroma/log_config.yaml from log-config (rw,path="log_config.yaml") /index_data from data (rw) /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-264h8 (ro) Conditions: Type Status PodScheduled False Volumes: data: Type: PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace) ClaimName: data-chroma-dev-chromadb-0 ReadOnly: false log-config: Type: ConfigMap (a volume populated by a ConfigMap) Name: chroma-dev-chromadb-log-config Optional: false kube-api-access-264h8: Type: Projected (a volume that contains injected data from multiple sources) TokenExpirationSeconds: 3607 ConfigMapName: kube-root-ca.crt ConfigMapOptional: <nil> DownwardAPI: true QoS Class: BestEffort Node-Selectors: <none> Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s node.kubernetes.io/unreachable:NoExecute op=Exists for 300s Events: Type Reason Age From Message ---- ------ ---- ---- ------- Warning FailedScheduling 23s default-scheduler 0/3 nodes are available: pod has unbound immediate PersistentVolumeClaims. preemption: 0/3 nodes are available: 3 No preemption victims found for incoming pod..

Стикер

Чёт с pvc