I did reproduce the same behaviour locally with a ...
# spicedb
v
I did reproduce the same behaviour locally with a fresh kube+operator+spicedb 1.15