mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
58 lines
3.4 KiB
Plaintext
58 lines
3.4 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * updating/preparing_for_updates/preparing-manual-creds-update.adoc
|
|
|
|
:_mod-docs-content-type: CONCEPT
|
|
|
|
[id="about-manually-maintained-credentials-upgrade_{context}"]
|
|
= Update requirements for clusters with manually maintained credentials
|
|
|
|
Before you update a cluster that uses manually maintained credentials with the Cloud Credential Operator (CCO), you must update the cloud provider resources for the new release.
|
|
|
|
If the cloud credential management for your cluster was configured using the CCO utility (`ccoctl`), use the `ccoctl` utility to update the resources. Clusters that were configured to use manual mode without the `ccoctl` utility require manual updates for the resources.
|
|
|
|
After updating the cloud provider resources, you must update the `upgradeable-to` annotation for the cluster to indicate that it is ready to update.
|
|
|
|
[NOTE]
|
|
====
|
|
The process to update the cloud provider resources and the `upgradeable-to` annotation can only be completed by using command-line tools.
|
|
====
|
|
|
|
[id="cco-platform-options_{context}"]
|
|
== Cloud credential configuration options and update requirements by platform type
|
|
|
|
Some platforms only support using the CCO in one mode. For clusters that are installed on those platforms, the platform type determines the credentials update requirements.
|
|
|
|
For platforms that support using the CCO in multiple modes, you must determine which mode the cluster is configured to use and take the required actions for that configuration.
|
|
|
|
.Credentials update requirements by platform type
|
|
image::334_OpenShift_cluster_updating_and_CCO_workflows_0523_4.11_B_AliCloud_patch.png[Decision tree showing the possible update paths for your cluster depending on the configured CCO credentials mode.]
|
|
|
|
{rh-openstack-first} and VMware vSphere::
|
|
These platforms do not support using the CCO in manual mode. Clusters on these platforms handle changes in cloud provider resources automatically and do not require an update to the `upgradeable-to` annotation.
|
|
+
|
|
Administrators of clusters on these platforms should skip the manually maintained credentials section of the update process.
|
|
|
|
{ibm-cloud-title} and Nutanix::
|
|
Clusters installed on these platforms are configured using the `ccoctl` utility.
|
|
+
|
|
Administrators of clusters on these platforms must take the following actions:
|
|
+
|
|
. Extract and prepare the `CredentialsRequest` custom resources (CRs) for the new release.
|
|
. Configure the `ccoctl` utility for the new release and use it to update the cloud provider resources.
|
|
. Indicate that the cluster is ready to update with the `upgradeable-to` annotation.
|
|
|
|
Microsoft Azure Stack Hub::
|
|
These clusters use manual mode with long-term credentials and do not use the `ccoctl` utility.
|
|
+
|
|
Administrators of clusters on these platforms must take the following actions:
|
|
+
|
|
. Extract and prepare the `CredentialsRequest` custom resources (CRs) for the new release.
|
|
. Manually update the cloud provider resources for the new release.
|
|
. Indicate that the cluster is ready to update with the `upgradeable-to` annotation.
|
|
|
|
Amazon Web Services (AWS), global Microsoft Azure, and {gcp-first}::
|
|
Clusters installed on these platforms support multiple CCO modes.
|
|
+
|
|
The required update process depends on the mode that the cluster is configured to use. If you are not sure what mode the CCO is configured to use on your cluster, you can use the web console or the CLI to determine this information.
|