New to KubeDB? Please start here.

Rotate Authentication of Microsoft SQL Server

This guide will give an overview on how KubeDB Ops-manager operator Rotate Authentication configuration.

Before You Begin

• You should be familiar with the following KubeDB concepts:
  • MSSQLServer
  • MSSQLServerOpsRequest

How Rotate MSSQLServer Authentication Configuration Process Works

The authentication rotation process for MSSQLServer using KubeDB involves the following steps:

1. A user first creates a MSSQLServer Custom Resource Object (CRO).

2. The KubeDB Provisioner operator continuously watches for MSSQLServer CROs.

3. When the operator detects a MSSQLServer CR, it provisions the required PetSets, along with related resources such as secrets, services, and other dependencies.

4. To initiate authentication rotation, the user creates a MSSQLServerOpsRequest CR with the desired configuration.

5. The KubeDB Ops-manager operator watches for MSSQLServerOpsRequest CRs.

6. Upon detecting a MSSQLServerOpsRequest, the operator pauses the referenced MSSQLServer object, ensuring that the Provisioner operator does not perform any operations during the authentication rotation process.

7. The Ops-manager operator then updates the necessary configuration (such as credentials) based on the provided MSSQLServerOpsRequest specification.

8. After applying the updated configuration, the operator restarts all MSSQLServer Pods so they come up with the new authentication environment variables and settings.

9. Once the authentication rotation is completed successfully, the operator resumes the MSSQLServer object, allowing the Provisioner operator to continue its usual operations.

In the next section, we will walk you through a step-by-step guide to rotating MSSQLServer authentication using the MSSQLServerOpsRequest CRD.