Hey folks. we've deployed spicedb in gke with disp...
# spicedb
n
Hey folks. we've deployed spicedb in gke with dispatch cluster disabled, even though the cpu usage is very low, we're seeing that the spicedb pod CPU is being throttled
Copy code
apiVersion: authzed.com/v1alpha1
kind: SpiceDBCluster
metadata:
  labels:
    argocd.argoproj.io/instance: spicedb-apps-uat
  name: spicedb-uat
  namespace: apps
  resourceVersion: "589311585"
  uid: 6b4326de-c83e-4c8b-9a57-7b713cc278af
spec:
  channel: stable
  config:
    datastoreEngine: postgres
    datastoreRevisionQuantizationInterval: 5s
    dispatchEnabled: "false"
    logFormat: json
    logLevel: debug
    replicas: 3
  patches:
  - kind: Deployment
    patch:
      spec:
        template:
          metadata:
            annotations:
              prometheus.io/path: /metrics
              prometheus.io/port: "9090"
              prometheus.io/scrape: "true"
          spec:
            containers:
            - name: spicedb
              resources:
                limits:
                  cpu: 101m
                  memory: 128Mi
                requests:
                  cpu: 101m
                  memory: 128Mi
  secretName: spicedb-uat
  version: v1.39.1
status:
  conditions:
  - lastTransitionTime: "2025-02-18T08:31:38Z"
    message: no TLS configured, consider setting "tlsSecretName"
    reason: WarningsPresent
    status: "True"
    type: ConfigurationWarning
  currentMigrationHash: n58fh56ch8hd8h5c6h67fh546h64bq
  image: ghcr.io/authzed/spicedb:v1.39.1
  migration: add-watch-api-index-to-relation-tuple-table
  observedGeneration: 13
  secretHash: nfch687h676h5b7hc6h666h55bh7q
  targetMigrationHash: n58fh56ch8hd8h5c6h67fh546h64bq
  version:
    attributes:
    - migration
    channel: stable
    name: v1.39.1
3 Views