https://authzed.com logo
Join Discord
Powered by
Hey guys I have a new question regarding
# spicedb
f
Hey guys, I have a new question regarding the watch api the watch api is enabled on postgres but still comes this error, but this error sounds like to be from spicedb and not postgres https://cdn.discordapp.com/attachments/844600078948630559/1161280899015508028/image.png?ex=6537ba1d&is=6525451d&hm=da5ce6b7926cab02032bdd5ebfe15a4a5263bf3bea07b730bc5889b2a6602be2&
v
is this a local deployment of SpiceDB or Authzed Serverless?
f
it is deployed with the k8s operator on kubernetes
on a self managed k8s cluster with a self managed postgres which is also running on k8s using kubegres
apparently it is because of the version. 1.24 doesn't support the watch api. but the issue if that I could not get 1.25 to run with the operator. I updated the deployment by hand
v
1.24 should support Watch API for sure
f
with 1.24 we get not implemented error and with 1.25 it works
the only issue is that when we set the version 1.25 in the 
SpiceDBCluster
definition, the operator will just not doing anything
only deploys the 1.24
v
watch api is definitely supported in both 1.24 and 1.25
Make sure to also use the latest operator version so it has the corresponding update graph. If a version is not part of the update graph, you can always set the 
image
field in in the SpiceDBCluster 
spec: config
f
I got it working with 1.24. the issue was the watch api in pgsql with kubegres. I found the correct place to set the config. thanks
v
Awesome
PreviousNext
Powered by