Passthrough mode is supported for Amazon Web Services (AWS), Microsoft Azure, Google Cloud Platform (GCP), {rh-openstack-first}, {rh-virtualization-first}, and VMware vSphere.
In passthrough mode, the Cloud Credential Operator (CCO) passes the provided cloud credential to the components that request cloud credentials. The credential must have permissions to perform the installation and complete the operations that are required by components in the cluster, but does not need to be able to create new credentials. The CCO does not attempt to create additional limited-scoped credentials in passthrough mode.
|
Note
|
Manual mode is the only supported CCO configuration for Microsoft Azure Stack Hub. |
When using the CCO in passthrough mode, ensure that the credential you provide meets the requirements of the cloud on which you are running or installing {product-title}. If the provided credentials the CCO passes to a component that creates a CredentialsRequest CR are not sufficient, that component will report an error when it tries to call an API that it does not have permissions for.
The credential you provide for passthrough mode in AWS must have all the requested permissions for all CredentialsRequest CRs that are required by the version of {product-title} you are running or installing.
To locate the CredentialsRequest CRs that are required, see Manually creating IAM for AWS.
The credential you provide for passthrough mode in Azure must have all the requested permissions for all CredentialsRequest CRs that are required by the version of {product-title} you are running or installing.
To locate the CredentialsRequest CRs that are required, see Manually creating IAM for Azure.
The credential you provide for passthrough mode in GCP must have all the requested permissions for all CredentialsRequest CRs that are required by the version of {product-title} you are running or installing.
To locate the CredentialsRequest CRs that are required, see Manually creating IAM for GCP.
To install an {product-title} cluster on {rh-openstack}, the CCO requires a credential with the permissions of a member user role.
To install an {product-title} cluster on {rh-virtualization}, the CCO requires a credential with the following privileges:
-
DiskOperator -
DiskCreator -
UserTemplateBasedVm -
TemplateOwner -
TemplateCreator -
ClusterAdminon the specific cluster that is targeted for {product-title} deployment
To install an {product-title} cluster on VMware vSphere, the CCO requires a credential with the following vSphere privileges:
| Category | Privileges |
|---|---|
Datastore |
Allocate space |
Folder |
Create folder, Delete folder |
vSphere Tagging |
All privileges |
Network |
Assign network |
Resource |
Assign virtual machine to resource pool |
Profile-driven storage |
All privileges |
vApp |
All privileges |
Virtual machine |
All privileges |
If CredentialsRequest CRs change over time as the cluster is upgraded, you must manually update the passthrough mode credential to meet the requirements. To avoid credentials issues during an upgrade, check the CredentialsRequest CRs in the release image for the new version of {product-title} before upgrading. To locate the CredentialsRequest CRs that are required for your cloud provider, see Manually creating IAM for AWS, Azure, or GCP.
When using passthrough mode, each component has the same permissions used by all other components. If you do not reduce the permissions after installing, all components have the broad permissions that are required to run the installer.
After installation, you can reduce the permissions on your credential to only those that are required to run the cluster, as defined by the CredentialsRequest CRs in the release image for the version of {product-title} that you are using.