I’m curious how my fellow K8s/Helm deployers troubleshoot erroring

dagster-user-deployments.deployments

The web UI only shows the error stating hat it can’t connect to the gRPC server, but curious the best way to surface the exception that is causing the server to fail, which I do now by

kubectl log <pod-name>

Thanks!

Hey dusty: there’s a —lazy-load-user-code argument that you can add to the dagsterApiGrpcArgs that will make it so that if there’s an error importing your code, the server stays up and displays the error in dagit instead of crashing

Ow that's useful! Is it documented somewhere? What i've been doing until now is catching it at docker build time. After the container is built I start it and probe the grpc server.

It’s in the api docs - there’s a good case to be made that it should be the default behavior I think

Indeed I also believe that should be the default. I always try to avoid giving our developers too much k8s access but due to this they have no way to understand what is going wrong.

We can probably do that for 1.1, might be a minor breaking change for some worklfows

@daniel That’s exactly what I needed! Much appreciated (again!)