$ oc create secret generic image-registry-private-configuration-user --from-file=REGISTRY_STORAGE_GCS_KEYFILE=<path_to_keyfile> --namespace openshift-image-registry
In addition to the configs.imageregistry.operator.openshift.io
and ConfigMap
resources, configuration is provided to the Operator by a separate secret
resource located within the openshift-image-registry
namespace.
The image-registry-private-configuration-user
secret provides
credentials needed for storage access and management. It overrides the default
credentials used by the Operator, if default credentials were found.
For GCS on GCP storage, the secret is expected to contain one key whose value is the contents of a credentials file provided by GCP:
REGISTRY_STORAGE_GCS_KEYFILE
Create an OpenShift Container Platform secret that contains the required keys.
$ oc create secret generic image-registry-private-configuration-user --from-file=REGISTRY_STORAGE_GCS_KEYFILE=<path_to_keyfile> --namespace openshift-image-registry
If the Registry Operator cannot create a Google Cloud Platform (GCP) bucket, you must set up the storage medium manually and configure the settings in the registry custom resource (CR).
A cluster on GCP with user-provisioned infrastructure.
To configure registry storage for GCP, you need to provide Registry Operator cloud credentials.
For GCS on GCP storage, the secret is expected to contain one key whose value is the contents of a credentials file provided by GCP:
REGISTRY_STORAGE_GCS_KEYFILE
Set up an Object Lifecycle Management policy to abort incomplete multipart uploads that are one day old.
Fill in the storage configuration in configs.imageregistry.operator.openshift.io/cluster
:
$ oc edit configs.imageregistry.operator.openshift.io/cluster
# ...
storage:
gcs:
bucket: <bucket-name>
projectID: <project-id>
region: <region-name>
# ...
You can secure your registry images that use a Google Cloud Storage bucket by setting public access prevention. |
The following configuration parameters are available for GCP GCS registry storage.
Parameter | Description |
---|---|
|
Bucket is the bucket name in which you want to store the registry’s data. It is optional and is generated if not provided. |
|
Region is the GCS location in which your bucket exists. It is optional and is set based on the installed GCS Region. |
|
ProjectID is the Project ID of the GCP project that this bucket should be associated with. It is optional. |
|
KeyID is the KMS key ID to use for encryption. It is optional because buckets are encrypted by default on GCP. This allows for the use of a custom encryption key. |