You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use custom secrets refs in our cluster, backed by External Secrets Operator; with secretsProvider set to internal.
When updating secrets' values, they are automatically rotated for Cassandra superuser and Reaper CQL. But not for Reaper UI – this required the pod restart.
Did you expect to see something different?
Updating the secret referenced by spec.reaper.uiUserSecretRef should automatically rotate the secret and not require the pod restart.
How to reproduce it (as minimally and precisely as possible):
Upgrade value of the spec.reaper.uiUserSecretRef secret and try to log in to Reaper UI – new credentials are not picked up; old credentials still work.
Restart the pod and try to log in again – new credentials are picked up.
Environment
K8ssandra Operator version: v1.20.2.
Kubernetes version information:
Kubernetes cluster kind: EKS
Manifests:
K8ssandra Operator Logs:
Anything else we need to know?:
┆Issue is synchronized with this Jira Story by Unito
┆Issue Number: K8OP-297
The text was updated successfully, but these errors were encountered:
What happened?
We use custom secrets refs in our cluster, backed by External Secrets Operator; with
secretsProvider
set tointernal
.When updating secrets' values, they are automatically rotated for Cassandra superuser and Reaper CQL. But not for Reaper UI – this required the pod restart.
Did you expect to see something different?
Updating the secret referenced by
spec.reaper.uiUserSecretRef
should automatically rotate the secret and not require the pod restart.How to reproduce it (as minimally and precisely as possible):
spec.reaper.uiUserSecretRef
secret and try to log in to Reaper UI – new credentials are not picked up; old credentials still work.Environment
K8ssandra Operator version: v1.20.2.
Kubernetes version information:
Kubernetes cluster kind: EKS
Manifests:
K8ssandra Operator Logs:
Anything else we need to know?:
┆Issue is synchronized with this Jira Story by Unito
┆Issue Number: K8OP-297
The text was updated successfully, but these errors were encountered: