Can't run in k8s

I'm trying to run the latest version via helm

helm upgrade --install --namespace rocketchat --create-namespace --set host=rocketchat.example.com --set ingress.enabled=true --set mongodb.auth.password=$(echo -n $(date +%s | sha256sum | base64 | head -c 32)),mongodb.auth.rootPassword=$(echo -n $(date +%s | sha256sum | base64 | head -c 32)) --set persistence.enabled=true --set persistence.storageClass=fast.ru-3a --set mongodb.persistence.storageClass=fast.ru-3a --set image.tag=4.7.0 rocketchat rocketchat/rocketchat

but the pods do not start

kubectl get pods -n rocketchat
NAME                                    READY   STATUS    RESTARTS      AGE
rocketchat-mongodb-0                    1/1     Running   0             10m
rocketchat-rocketchat-86d9df64f-kmj6f   0/1     Running   4 (48s ago)   10m

I see that it cannot be connected and therefore constantly restarts

2m55s       Normal    Killing                  pod/rocketchat-rocketchat-86d9df64f-kmj6f            Container rocketchat failed liveness probe, will be restarted
2m23s       Normal    Created                  pod/rocketchat-rocketchat-86d9df64f-kmj6f            Created container rocketchat
2m23s       Normal    Pulled                   pod/rocketchat-rocketchat-86d9df64f-kmj6f            Container image "registry.rocket.chat/rocketchat/rocket.chat:4.7.0" already present on machine
2m21s       Normal    Started                  pod/rocketchat-rocketchat-86d9df64f-kmj6f            Started container rocketchat
85s         Warning   Unhealthy                pod/rocketchat-rocketchat-86d9df64f-kmj6f            Readiness probe failed: Get "http://10.10.215.27:3000/api/info": dial tcp 10.10.215.27:3000: connect: connection refused
70s         Warning   Unhealthy                pod/rocketchat-rocketchat-86d9df64f-kmj6f            Liveness probe failed: Get "http://10.10.215.27:3000/api/info": dial tcp 10.10.215.27:3000: connect: connection refused

what am i missing and how can i run it to make it work?

Start with the Helm chart configuration represented by the command and inspect the Rocket.Chat pod logs alongside the readiness and liveness probe settings. Reproduce the deployment with kubectl and determine what prevents port 3000 from accepting connections; done means the pod becomes ready without probe-triggered restarts.