Skip to content

Commit 158de24

Browse files
authored
Update howto-credential-rotation.md
Update the howto-credential-rotation guide to include newly supported etcd and local storage credential rotation support. Remove statements with listed credentials to reduce the amount of repetition and be more generic for adding more credentials in the future.
1 parent aeca942 commit 158de24

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

articles/operator-nexus/howto-credential-rotation.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -31,24 +31,26 @@ The Operator Nexus Platform offers a managed credential rotation process that au
3131
- Baseboard Management Controller (BMC)
3232
- Pure Storage Array Administrator
3333
- Console User for emergency access
34+
- etcd
35+
- Local path storage
3436

3537
When a new Cluster is created, the credentials are automatically rotated during deployment. The managed credential process then automatically rotates these credentials every 60 days. The updated credentials are written to the key vault associated with the Cluster resource. The last rotation timestamps are currently not visible to users, but is a planned enhancement to the Operator Nexus Platform.
3638

3739
> [!NOTE]
38-
> The introduction of this capability enables auto-rotation for existing instances. If the BMC, Storage Administrator or Console User credentials have not been rotated within the last 60 days, they will be rotated at the time of upgrade.
40+
> The introduction of this capability enables auto-rotation for existing instances. If any of the supported credentials have not been rotated within the last 60 days, they will be rotated at the time of upgrade.
3941
4042
Operator Nexus also provides a service for preemptive rotation of the above Platform credentials. This service is available to customers upon request through a support ticket. Credential rotation for Operator Nexus Fabric devices also requires a support ticket. Instructions for generating a support request are described in the next section.
4143

4244
## Create a support request
4345

4446
Users raise credential rotation requests by [contacting support](https://portal.azure.com/?#blade/Microsoft_Azure_Support/HelpAndSupportBlade). These details are required in order to perform the credential rotation on the requested target instance:
4547

46-
- Type of credential that needs to be rotated. Specify if the request is for a fabric device, BMC, Storage Admin, Console User or for all four types.
48+
- Type of credential that needs to be rotated.
4749
- Provide Tenant ID.
4850
- Provide Subscription ID.
4951
- Provide Resource Group Name in which the target cluster or fabric resides based on type of credential that needs to be rotated.
5052
- Provide Target Cluster or Fabric Name based on type of credential that needs to be rotated.
5153
- Provide Target Cluster or Fabric Azure Resource Manager (ARM) ID based on type of credential that needs to be rotated.
52-
- Provide the Customer Key Vault ID where rotated credentials are written. Only applies to Operator Nexus Fabric devices. BMC, Pure Admin & Console User credential rotations use the key vault provided on the Cluster.
54+
- Provide the Customer Key Vault ID where rotated credentials are written.
5355

5456
For more information about Support plans, see [Azure Support plans](https://azure.microsoft.com/support/plans/response/).

0 commit comments

Comments
 (0)