mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
55 lines
2.5 KiB
Plaintext
55 lines
2.5 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * operators/operator-reference.adoc
|
|
// * installing/overview/cluster-capabilities.adoc
|
|
|
|
// operators/operator-reference.adoc
|
|
ifeval::["{context}" == "operator-reference"]
|
|
:operator-ref:
|
|
endif::[]
|
|
|
|
// installing/overview/cluster-capabilities.adoc
|
|
ifeval::["{context}" == "cluster-capabilities"]
|
|
:cluster-caps:
|
|
endif::[]
|
|
|
|
:_mod-docs-content-type: REFERENCE
|
|
[id="cluster-image-registry-operator_{context}"]
|
|
ifdef::operator-ref[= Cluster Image Registry Operator]
|
|
ifdef::cluster-caps[= Cluster Image Registry capability]
|
|
|
|
ifdef::cluster-caps[]
|
|
The Cluster Image Registry Operator provides features for the `ImageRegistry` capability.
|
|
endif::[]
|
|
|
|
The Cluster Image Registry Operator manages a singleton instance of the {product-registry}. It manages all configuration of the registry, including creating storage.
|
|
|
|
On initial start up, the Operator creates a default `image-registry` resource instance based on the configuration detected in the cluster. This indicates what cloud storage type to use based on the cloud provider.
|
|
|
|
If insufficient information is available to define a complete `image-registry` resource, then an incomplete resource is defined and the Operator updates the resource status with information about what is missing.
|
|
|
|
The Cluster Image Registry Operator runs in the `openshift-image-registry` namespace and it also manages the registry instance in that location. All configuration and workload resources for the registry reside in that namespace.
|
|
|
|
ifdef::cluster-caps[]
|
|
In order to integrate the image registry into the cluster's user authentication and authorization system, a service account token secret and an image pull secret are generated for each service account in the cluster.
|
|
|
|
[IMPORTANT]
|
|
====
|
|
If you disable the `ImageRegistry` capability or if you disable the integrated {product-registry} in the Cluster Image Registry Operator's configuration, the service account token secret and image pull secret are not generated for each service account.
|
|
====
|
|
|
|
If you disable the `ImageRegistry` capability, you can reduce the overall resource footprint of {product-title} in resource-constrained environments. Depending on your deployment, you can disable this component if you do not need it.
|
|
endif::[]
|
|
|
|
|
|
== Project
|
|
|
|
link:https://github.com/openshift/cluster-image-registry-operator[cluster-image-registry-operator]
|
|
|
|
ifeval::["{context}" == "operator-reference"]
|
|
:!operator-ref:
|
|
endif::[]
|
|
ifeval::["{context}" == "cluster-capabilities"]
|
|
:!cluster-caps:
|
|
endif::[]
|