The operator is not upgrading my cluster to v1.18.0

[imclem]

Hi there,

I've juste installed the operator yesterday and created my first cluster. After creation I've specified that I want the v1.18.0 to run (as I'm getting warning from zed CLI). My cluster is in the following state for multiple hours:

NAME                             AGE   CHANNEL   DESIRED   CURRENT   WARNINGS   MIGRATING   UPDATING   INVALID  
spicedb-mycoach-infrastructure   15h   stable    v1.18.0   v1.17.0   True

I've set the desired version in spec.version, should I do something else for my cluster to update ?

Thanks.

[ecordell]

Can you share the status of the SpiceDBCluster object? From what you've shared, there should be a warning on it.

[imclem]

Yes it is complaining about tls.

Is there a way of removing this warning ? I'm running the cluster internally nothing is exposed to the outside world I won't need tls there.

Here's the output of describing the cluster:

Name:         spicedb-mycoach-infrastructure
Namespace:    default
Labels:       app.kubernetes.io/managed-by=Helm
Annotations:  meta.helm.sh/release-name: mycoach-infrastructure
              meta.helm.sh/release-namespace: default
API Version:  authzed.com/v1alpha1
Kind:         SpiceDBCluster
Metadata:
  Creation Timestamp:  2023-03-23T17:26:40Z
  Generation:          2
  Managed Fields:
    API Version:  authzed.com/v1alpha1
    Fields Type:  FieldsV1
    fieldsV1:
      f:metadata:
        f:annotations:
          f:meta.helm.sh/release-name:
          f:meta.helm.sh/release-namespace:
        f:labels:
          f:app.kubernetes.io/managed-by:
      f:status:
        f:conditions:
        f:currentMigrationHash:
        f:image:
        f:migration:
        f:observedGeneration:
        f:secretHash:
        f:targetMigrationHash:
        f:version:
          f:attributes:
          f:channel:
          f:name:
    Manager:      spicedb-operator
    Operation:    Apply
    Subresource:  status
    Time:         2023-03-23T17:58:00Z
    API Version:  authzed.com/v1alpha1
    Fields Type:  FieldsV1
    fieldsV1:
      f:metadata:
        f:annotations:
          .:
          f:meta.helm.sh/release-name:
          f:meta.helm.sh/release-namespace:
        f:labels:
          .:
          f:app.kubernetes.io/managed-by:
      f:spec:
        .:
        f:channel:
        f:config:
          .:
          f:datastoreEngine:
          f:replicas:
        f:secretName:
        f:version:
    Manager:         Go-http-client
    Operation:       Update
    Time:            2023-03-23T17:57:48Z
  Resource Version:  323995626
  UID:               3fd90ca2-f928-4fc1-bb16-326def7e6ae6
Spec:
  Channel:  stable
  Config:
    Datastore Engine:  mysql
    Replicas:          3
  Secret Name:         spicedb-mycoach-infrastructure
  Version:             v1.18.0
Status:
  Conditions:
    Last Transition Time:  2023-03-23T17:26:40Z
    Message:               no TLS configured, consider setting "tlsSecretName"
    Reason:                WarningsPresent
    Status:                True
    Type:                  ConfigurationWarning
  Current Migration Hash:  n654hf7h5c4h5c7h96h7dh56bh5f5q
  Image:                   ghcr.io/authzed/spicedb:v1.17.0
  Migration:               add_caveat
  Observed Generation:     2
  Secret Hash:             n645h599h694hd6h96h547h695h688q
  Target Migration Hash:   n654hf7h5c4h5c7h96h7dh56bh5f5q
  Version:
    Attributes:
      migration
    Channel:  stable
    Name:     v1.17.0
Events:       <none>

[ecordell]

What version of the operator are you running? v1.18.0 was added to the update graph in https://github.com/authzed/spicedb-operator/releases/tag/v1.4.0

It should show "AvailableVersions" in the status, and I don't see anything there.

Is there a way of removing this warning ? I'm running the cluster internally nothing is exposed to the outside world I won't need tls there.

Currently, no, though it's just a warning (it doesn't affect anything). Would you like to file an issue for an option to disable it?

[imclem]

What version of the operator are you running? v1.18.0 was added to the update graph in https://github.com/authzed/spicedb-operator/releases/tag/v1.4.0

I'm running v1.3.0. I will try upgrading to the v1.4.0 and check if the cluster upgrades to v1.18.0.

Currently, no, though it's just a warning (it doesn't affect anything). Would you like to file an issue for an option to disable it?

Will do yes.

Thanks

[imclem]

After upgrading the operator to the v1.4.0, the cluster got upgraded to v1.18.0 instantly.

I misunderstood how this worked, thanks a lot for your help.