as to your error that is a very weird one Can you share the

Question

as to your error that is a very weird one Can you share the ENVs of your SpiceDB `Deployment` also logs

ensonic · Answer

https gist github com ensonic 1b6bf557a7028663665ec58a91008b3d

vroldanbet · Answer

like I tested the PR locally and check requests seem to work

vroldanbet · Answer

let me have a look

vroldanbet · Answer

dispatch is still set that s not what the PR does

vroldanbet · Answer

```SPICEDB DISPATCH UPSTREAM ADDR kubernetes dev default dispatch```

vroldanbet · Answer

the PR fixes making sure that ENV is not set at all

ensonic · Answer

I ve just rebuild from your PR repushed the image and deleted dev spicedb deployment and recreated it and the env is set

ensonic · Answer

I ll add some logging to your change to double check that I am running the changed code

ensonic · Answer

It works now

ensonic · Answer

kubectl set image only restarts the pod if the image name changed

ensonic · Answer

since iI first build from head and then from your PR the 2nd round had no effect

vroldanbet · Answer

glad to hear there is usually a lot of moving parts in a kube setup and is easy to miss those

ensonic · Answer

sorry for the noise Hope this can be merged soon But at least I can test now

vroldanbet · Answer

not at all you are helping the projects get better for the whole community so we appreciate you bringing those rough edges up