Startup probes
# spicedb
m
So where do I go to set a connection timeout? I am getting the following error Warmup probe failed: parsed option: > addr=localhost:50051 conn_timeout=1s rpc_timeout=1s > tls=true > no-verify=true > ca-cert= > client-cert= > client-key= > server-name= > alts=false > spiffe=false Failed to set connection timeout: Connection to service "localhost:50051" failed within 1 second.
v
That's part of the startup probes. Are you creating your own Deployment definition? The container comes with grpc-health-probe command, which should allow you to set the timeout
m
v
--http-enabled
is not a command line argument to the
grpc_health_probe
command. I don't see anything unusual in that liveness probe. I'd say your container is failing to start. Have you checked what your SpiceDB container logs say?
m
I don't see any errors in the logs, it just seems to happen irregularly and intermittently. The command line args were referring to the container command line args, not the Prob command. Anyway, the bottom line is that I can't get inside the pod, right? Thanks for the help 🙂
v
you can get inside of the pod if you use the
-debug
containers
and irregularly / intermitently feels like the process is becoming saturated, I'd suggest looking into the metrics to see if something stands out
35 Views