Add or Update a Red Hat Pull Secret on ARO
This content is authored by Red Hat experts, but has not yet been tested on every supported configuration.
When deploying an Azure Red Hat OpenShift (ARO) cluster, omitting a Red Hat pull secret results in a “limited” configuration. While this allows the cluster to function using core service images, it restricts access to the broader Red Hat ecosystem, including Red Hat container registries, along with other content like operators from OperatorHub.
Microsoft’s official guidance involves a manual process for updating these credentials. You can find those steps here .
To eliminate the manual overhead of merging and updating secrets, we have developed a Helm Chart that automates the entire workflow. This tool intelligently concatenates your Red Hat pull secret with the existing cluster secret, ensuring seamless access to Red Hat resources without the risk of manual configuration errors.
Prerequisites
- Helm CLI
Prepare Environment
Add the Cloud Experts Helm Chart repository to your Helm environment:
Update your Helm repositories to pull the latest content:
Deploy the Helm Chart
Before Deploying the chart you need it to adopt the existing pull secret
Download your pull secret from the Red Hat OpenShift Cluster Manager .
Update the pull secret using the Helm Chart:
Once the pull secret is updated, enable the OperatorHub sources:
