Skip to content

Commit 3ff33fe

Browse files
authored
Merge pull request #86900 from jeana-redhat/OCPBUGS-48192-clarify-mint-mode-root-role
OCPBUGS-48192: clarifying the role of the root cred in CCO mint mode
2 parents 4fc9bd2 + 5434c6a commit 3ff33fe

File tree

3 files changed

+20
-8
lines changed

3 files changed

+20
-8
lines changed

authentication/managing_cloud_provider_credentials/cco-mode-mint.adoc

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,9 +11,14 @@ Mint mode is the default Cloud Credential Operator (CCO) credentials mode for {p
1111
[id="mint-mode-about"]
1212
== Mint mode credentials management
1313

14-
For clusters that use the CCO in mint mode, the administrator-level credential is stored in the `kube-system` namespace. The CCO uses the `admin` credential to process the `CredentialsRequest` objects in the cluster and create users for components with limited permissions.
14+
For clusters that use the CCO in mint mode, the administrator-level credential is stored in the `kube-system` namespace.
15+
The CCO uses the `admin` credential to process the `CredentialsRequest` objects in the cluster and create users for components with limited permissions.
1516

16-
With mint mode, each cluster component has only the specific permissions it requires. The automatic, continuous reconciliation of cloud credentials in mint mode allows actions that require additional credentials or permissions, such as upgrading, to proceed.
17+
With mint mode, each cluster component has only the specific permissions it requires.
18+
Cloud credential reconciliation is automatic and continuous so that components can perform actions that require additional credentials or permissions.
19+
20+
For example, a minor version cluster update (such as updating from {product-title} 4.16 to 4.17) might include an updated `CredentialsRequest` resource for a cluster component.
21+
The CCO, operating in mint mode, uses the `admin` credential to process the `CredentialsRequest` resource and create users with limited permissions to satisfy the updated authentication requirements.
1722

1823
[NOTE]
1924
====

modules/manually-removing-cloud-creds.adoc

Lines changed: 10 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,21 +1,27 @@
11
// Module included in the following assemblies:
22
//
3-
// * post_installation_configuration/cluster-tasks.adoc
3+
// * post_installation_configuration/changing-cloud-credentials-configuration.adoc
44

55
:_mod-docs-content-type: PROCEDURE
66
[id="manually-removing-cloud-creds_{context}"]
77
= Removing cloud provider credentials
88

9-
After installing an {product-title} cluster with the Cloud Credential Operator (CCO) in mint mode, you can remove the administrator-level credential secret from the `kube-system` namespace in the cluster. The administrator-level credential is required only during changes that require its elevated permissions, such as upgrades.
9+
For clusters that use the Cloud Credential Operator (CCO) in mint mode, the administrator-level credential is stored in the `kube-system` namespace.
10+
The CCO uses the `admin` credential to process the `CredentialsRequest` objects in the cluster and create users for components with limited permissions.
11+
12+
After installing an {product-title} cluster with the CCO in mint mode, you can remove the administrator-level credential secret from the `kube-system` namespace in the cluster.
13+
The CCO only requires the administrator-level credential during changes that require reconciling new or modified `CredentialsRequest` custom resources, such as minor cluster version updates.
1014

1115
[NOTE]
1216
====
13-
Prior to a non z-stream upgrade, you must reinstate the credential secret with the administrator-level credential. If the credential is not present, the upgrade might be blocked.
17+
Before performing a minor version cluster update (for example, updating from {product-title} 4.16 to 4.17), you must reinstate the credential secret with the administrator-level credential.
18+
If the credential is not present, the update might be blocked.
1419
====
1520

1621
.Prerequisites
1722

18-
* Your cluster is installed on a platform that supports removing cloud credentials from the CCO. Supported platforms are AWS and GCP.
23+
* Your cluster is installed on a platform that supports removing cloud credentials from the CCO.
24+
Supported platforms are AWS and GCP.
1925
2026
.Procedure
2127

post_installation_configuration/changing-cloud-credentials-configuration.adoc

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -31,15 +31,16 @@ include::modules/manually-rotating-cloud-creds.adoc[leveloffset=+2]
3131

3232
[role="_additional-resources"]
3333
.Additional resources
34+
* xref:../authentication/managing_cloud_provider_credentials/cco-mode-mint.adoc#cco-mode-mint[The Cloud Credential Operator in mint mode]
35+
* xref:../authentication/managing_cloud_provider_credentials/cco-mode-passthrough.html#cco-mode-passthrough[The Cloud Credential Operator in passthrough mode]
3436
* xref:../storage/container_storage_interface/persistent-storage-csi-vsphere.adoc#persistent-storage-csi-vsphere[vSphere CSI Driver Operator]
3537

3638
//Removing cloud provider credentials manually
3739
include::modules/manually-removing-cloud-creds.adoc[leveloffset=+2]
3840

39-
//These additional resources are for the "Rotating or removing cloud provider credentials" section, do not separate them from that content.
4041
[role="_additional-resources"]
4142
.Additional resources
42-
* xref:../authentication/managing_cloud_provider_credentials/cco-mode-passthrough.adoc#admin-credentials-root-secret-formats_cco-mode-passthrough[Admin credentials root secret format]
43+
* xref:../authentication/managing_cloud_provider_credentials/cco-mode-mint.adoc#cco-mode-mint[The Cloud Credential Operator in mint mode]
4344

4445
[id="post-install-enable-token-auth_{context}"]
4546
== Enabling token-based authentication

0 commit comments

Comments
 (0)