spicedb-operator
spicedb-operator copied to clipboard
Kubernetes controller for managing instances of SpiceDB
When the spicedb operator starts up, I see this line in the logs: > E0415 14:22:57.432900 1 controller.go:288] syncOwnedResource called on unknown object (authzed.com/v1alpha1, Resource=spicedbclusters::ccc-work-kgw-a-2/spicedb): spicedbclusters.authzed.com "spicedb" not found ......
Support for multiple preshared keys [exists](https://github.com/authzed/spicedb/issues/288) in spicedb, but I only see documentation for setting a single preshared key, via ```preshared_key``` in the config secret. Can multiple keys be set?...
Bumps the gomod-version group with 12 updates: | Package | From | To | | --- | --- | --- | | [github.com/evanphx/json-patch](https://github.com/evanphx/json-patch) | `5.7.0+incompatible` | `5.9.0+incompatible` | | [github.com/go-logr/logr](https://github.com/go-logr/logr)...
It's mounted under `spicedb-db-tls` (which will need to be referenced in the `datastore_uri` in the secret), but this is not documented well.
I'm currently trying to set up the spicedb-operator in our Kubernetes cluster but I'm running into an issue around permissions. Currently the operator is failing to start in our cluster...
If you don't completely control how the datastore_uri is generated(and possibly regenerated at any time), such as with a Postgres operator, creating a secret for the SpiceDBCluster config is hard....
I'm working on running spicedb inside an istio-enabled namespace with mTLS in STRICT mode. I noticed that when I enabled istio, 1 of the 2 spicedb pods would start up...
Hello, I had an initial looks at the operator, I wonder if there is any way to have autoscaling like https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/ ?
Bumps [google.golang.org/grpc](https://github.com/grpc/grpc-go) from 1.49.0 to 1.57.0. Release notes Sourced from google.golang.org/grpc's releases. Release 1.57.0 API Changes resolver: remove deprecated Target.Scheme and Target.Authority. Use URL.Scheme and URL.Host instead, respectively (#6363) Behavior...
**Summary** Add CPU and memory request/limits for SpiceDB Cluster deployment **Details** The SpiceDB Deployment manifests are missing resource specs, which means that the resulting pod will have [`BestEffort` quality of...