Blame docs/operations/ci/configuring_image_registry.md

47c289
## Image Registry
47c289
47c289
### Resources
47c289
- [1] https://docs.openshift.com/container-platform/4.4/registry/configuring_registry_storage/configuring-registry-storage-baremetal.html
47c289
47c289
47c289
### Prerequisites
47c289
47c289
- Cluster administrator permissions.
47c289
- A cluster on bare metal.
47c289
- Provision persistent storage for your cluster, such as Red Hat OpenShift Container Storage. To deploy a private image registry, your storage must provide ReadWriteMany access mode.
47c289
- Must have "100Gi" capacity.
47c289
47c289
47c289
47c289
To start the image registry, you must change ManagementState Image Registry Operator configuration from Removed to Managed.
47c289
Leave the claim field blank to allow the automatic creation of an image-registry-storage PVC.
47c289
47c289
47c289
```
47c289
$ oc edit configs.imageregistry/cluster
47c289
apiVersion: imageregistry.operator.openshift.io/v1
47c289
kind: Config
47c289
metadata:
47c289
...
47c289
spec:
47c289
...
47c289
  managementState: Managed
47c289
  storage:
47c289
    pvc:
47c289
      claim:
47c289
...
47c289
```
47c289
47c289
47c289
We want to enable the image pruner, to occationally prune images in the registry.
47c289
47c289
```
47c289
$ oc edit imagepruner.imageregistry/cluster
47c289
apiVersion: imageregistry.operator.openshift.io/v1
47c289
kind: ImagePruner
47c289
metadata:
47c289
  name: cluster
47c289
spec:
47c289
  suspend: false
47c289
...
47c289
```
47c289
47c289
47c289
Check the status of the deployment:
47c289
47c289
```
47c289
oc get clusteroperator image-registry
47c289
```
47c289