Skip to content

Commit b80d845

Browse files
Update for Redis, Valkey, Rabbitmq
Signed-off-by: Neaj Morshad <[email protected]>
1 parent e89b46c commit b80d845

File tree

1 file changed

+7
-42
lines changed

1 file changed

+7
-42
lines changed

content/post/kubedb-v2025.5.30/index.md

Lines changed: 7 additions & 42 deletions
Original file line numberDiff line numberDiff line change
@@ -449,9 +449,8 @@ This update ensures that KubeDB ProxySQL remains compatible with modern MySQL au
449449
We have added a new ProxySQL version `3.0.1`.
450450

451451
## RabbitMQ
452-
453-
OpsRequest
454-
RotateAuth OpsRequest for rabbitmq has been added. If a user wants to update the authentication credentials for a particular database, they can create an OpsRequest of type `RotateAuth` with or without referencing an authentication secret. If the secret is not referenced, the ops-manager operator will create a new credential and update the current secret. Here is the Yaml for rotating authentication credentials for a Rabbitmq cluster using RabbitMQOpsRequest.
452+
### New OpsRequest Support
453+
`RotateAuth` OpsRequest for `RabbitMQ` has been added. If a user wants to update the authentication credentials for a particular database, they can create an OpsRequest of type `RotateAuth` with or without referencing an authentication secret. If the secret is not referenced, the ops-manager operator will create a new credential and update the current secret. Here is the Yaml for rotating authentication credentials for a Rabbitmq cluster using RabbitMQOpsRequest.
455454
```yaml
456455
apiVersion: ops.kubedb.com/v1alpha1
457456
kind: RabbitMQOpsRequest
@@ -499,10 +498,9 @@ Finally, the operator will update the database cluster with the new credential a
499498
`RotateAuth` OpsRequest for `Redis` has been added. If a user wants to update the authentication credentials for a particular database, they can create an `OpsRequest` of type `RotateAuth` with or without referencing an authentication secret.
500499

501500
#### Rotate Authentication Without Referencing a Secret
502-
If the secret is not referenced, the `ops-manager` operator will create new credentials and update the existing secret with the new credentials.
501+
If the secret is not referenced, the `ops-manager` operator will create new credentials and update the existing secret with the new credentials, keeping previous credentials under the keys `username.prev` and `password.prev`.
503502

504503
Example YAML:
505-
506504
```yaml
507505
apiVersion: ops.kubedb.com/v1alpha1
508506
kind: RedisOpsRequest
@@ -546,45 +544,12 @@ spec:
546544
secretRef:
547545
name: my-auth
548546
```
549-
Finally, the operator will update the database with the new credential and the old credentials will be stored in the secret with keys `username.prev` and `password.prev`. We have added a field `.spec.authSecret.activeFrom` to the db yaml which refers to the timestamp of the credential is active from. We also add an annotation `kubedb.com/auth-active-from` in currently using auth secret which refers to the active from time of this secret.
550-
551-
**Note:** The `RotateAuth` OpsRequest can be applied to **Valkey** in the same way as it is for **Redis**.
547+
We have also added a field `.spec.authSecret.activeFrom` to the db yaml which refers to the timestamp of the credential is active from. We also add an annotation `kubedb.com/auth-active-from` in currently using auth secret which refers to the active from time of this secret.
552548

553549
## RedisSentinel
554550

555551
### Rotate Authentication Credentials for RedisSentinel
556-
`RotateAuth` OpsRequest for `RedisSentinel` has been added. If a user wants to update the authentication credentials for `RedisSentinel`, they can create an `OpsRequest` of type `RotateAuth` with or without referencing an authentication secret.
557-
#### Rotate Authentication Without Referencing a Secret
558-
If the secret is not referenced, the `ops-manager` operator will create new credentials and update the existing secret with the new credentials.
559-
560-
Example YAML:
561-
```yaml
562-
apiVersion: ops.kubedb.com/v1alpha1
563-
kind: RedisSentinelOpsRequest
564-
metadata:
565-
name: redis-sentinel-rotate
566-
namespace: demo
567-
spec:
568-
type: RotateAuth
569-
databaseRef:
570-
name: sen-demo
571-
```
572-
573-
#### Rotate Authentication With a Referenced Secret
574-
If a secret is referenced, the operator will update the `.spec.authSecret.name` field with the new secret name. Archives the old credentials in the newly created secret under the keys `username.prev` and `password.prev`.
575-
576-
New Secret Example:
577-
```yaml
578-
apiVersion: v1
579-
data:
580-
password: bXlQYXNzd29yZA==
581-
username: ZGVmYXVsdA==
582-
kind: Secret
583-
metadata:
584-
name: my-auth
585-
namespace: demo
586-
type: kubernetes.io/basic-auth
587-
```
552+
`RotateAuth` OpsRequest for `RedisSentinel` has been added as well. If a user wants to update the authentication credentials for `RedisSentinel`, they can create an `OpsRequest` of type `RotateAuth` with or without referencing an authentication secret in the same way as mentioned for `Redis`.
588553

589554
Example YAML with Secret Reference:
590555
```yaml
@@ -601,9 +566,9 @@ spec:
601566
secretRef:
602567
name: my-auth
603568
```
604-
Finally, the operator will update the sentinel with the new credential and the old credentials will be stored in the secret with keys `username.prev` and `password.prev`. We have added a field `.spec.authSecret.activeFrom` to the db yaml which refers to the timestamp of the credential is active from. We also add an annotation `kubedb.com/auth-active-from` in currently using auth secret which refers to the active from time of this secret.
605569

606-
**Note:** The `RotateAuth` OpsRequest can be applied to **Valkeysentinel** in the same way as it is for **Redissentinel**.
570+
**Note:** The `RotateAuth` OpsRequest can also be applied for the `Valkey` database as well in the same way shown above for Redis.
571+
607572
## SingleStore
608573

609574
In this release, we have addressed a bug related to the SingleStore Backup process. Previously the `databases` flag was not functioning properly, which occasionally caused issues during backup. This issue has been fixed in this release.

0 commit comments

Comments
 (0)