https://authzed.com logo
Join Discord
Powered by
can i move the operator beyond that
# spicedb
c
can i move the operator beyond that warning? it just seems to be hanging out waiting
e
can you provide more details? you shouldn't have to provide tls certs for it to run spicedb
c
sure. what would you like me to provide?
e
can you share your SpiceDBCluster object?
c
Copy code
---
apiVersion: authzed.com/v1alpha1
kind: SpiceDBCluster
metadata:
  name: spicedb-master
spec:
  channel: stable 
  version: v1.27.0
  config:
    logLevel: debug
    replicas: 3
    datastoreEngine: postgres
    httpEnabled: "true"
  secretName: spicedb-config
e
what about the status?
c
and the yaml repr of it in cluster is
Copy code
Kind:         SpiceDBCluster
Metadata:
  Creation Timestamp:  2023-09-10T23:00:06Z
  Generation:          6
  Resource Version:    153802876
  UID:                 681c385b-32f6-41d3-980d-2faebcbcda5a
Spec:
  Channel:  stable
  Config:
    Datastore Engine:  postgres
    Http Enabled:      true
    Log Level:         debug
    Replicas:          3
  Secret Name:         spicedb-config
  Version:             v1.27.0
Status:
  Conditions:
    Last Transition Time:  2023-09-10T23:00:06Z
    Message:               no TLS configured, consider setting "tlsSecretName"
    Reason:                WarningsPresent
    Status:                True
    Type:                  ConfigurationWarning
  Current Migration Hash:  n575h558h5dch5cfh9dh565h544h555q
  Image:                   ghcr.io/authzed/spicedb:v1.26.0
  Migration:               add-rel-by-alive-resource-relation-subject
  Observed Generation:     6
  Secret Hash:             n96h5cch5c6h98h576h7dh67h5d6q
  Target Migration Hash:   n575h558h5dch5cfh9dh565h544h555q
  Version:
    Attributes:
      migration
    Channel:  stable
    Name:     v1.26.0
Events:       <none>
e
can you change v1.27.0 in the spec to v1.26.0?
because of regressions we haven't published 1.27.0 into the stable channel
c
ahhh. ok. lemme do that. i was just walking up through the gh releases
i had previously had it at 1.26.0
e
it looks like it should be running at 1.26.0 right now?
you don't see pods?
c
its running at 1.26.0 right now yeah
e
ah okay
c
and i have pods for it at 1.26.0
e
I believe there should've been a status message saying 1.27.0 isn't in the channel
so that may be a bug
c
i had just been making my way up through the releases here https://github.com/authzed/spicedb/releases?page=1
and had got to 1.27.0 and encountered this
e
yeah, we're pretty conservative about the stable channel
there should be a new version in it in the next week
c
what/where can i see the current latest in stable?
so i might know when to stop upgrading in the future
e
or you can run a 
SpiceDBCluster
without 
version
set and it will default to the latest
c
awesome! thanks for the help!
PreviousNext
Powered by