Image configuration resources

Use the following procedure to configure image registries.

Image controller configuration parameters

The image.config.openshift.io/cluster resource holds cluster-wide information about how to handle images. The canonical, and only valid name is cluster. Its spec offers the following configuration parameters.

ParameterDescription

allowedRegistriesForImport

Limits the container image registries from which normal users can import images. Set this list to the registries that you trust to contain valid images, and that you want applications to be able to import from. Users with permission to create images or ImageStreamMappings from the API are not affected by this policy. Typically only cluster administrators have the appropriate permissions.

Every element of this list contains a location of the registry specified by the registry domain name.

domainName: Specifies a domain name for the registry. In case the registry uses a non-standard 80 or 443 port, the port should be included in the domain name as well.

insecure: Insecure indicates whether the registry is secure or insecure. By default, if not otherwise specified, the registry is assumed to be secure.

additionalTrustedCA

A reference to a config map containing additional CAs that should be trusted during image stream import, pod image pull, openshift-image-registry pullthrough, and builds.

The namespace for this config map is openshift-config. The format of the config map is to use the registry hostname as the key, and the PEM-encoded certificate as the value, for each additional registry CA to trust.

externalRegistryHostnames

Provides the hostnames for the default external image registry. The external hostname should be set only when the image registry is exposed externally. The first value is used in publicDockerImageRepository field in image streams. The value must be in hostname[:port] format.

registrySources

Contains configuration that determines how the container runtime should treat individual registries when accessing images for builds and pods. For instance, whether or not to allow insecure access. It does not contain configuration for the internal cluster registry.

insecureRegistries: Registries which do not have a valid TLS certificate or only support HTTP connections.

blockedRegistries: Denylisted for image pull and push actions. All other registries are allowed.

allowedRegistries: Allowlisted for image pull and push actions. All other registries are blocked.

Either blockedRegistries or allowedRegistries can be set, but not both.

When the allowedRegistries parameter is defined, all registries, including registry.redhat.io and quay.io registries and the default internal image registry, are blocked unless explicitly listed. When using the parameter, to prevent pod failure, add all registries including the registry.redhat.io and quay.io registries and the internalRegistryHostname to the allowedRegistries list, as they are required by payload images within your environment. For disconnected clusters, mirror registries should also be added.

The status field of the image.config.openshift.io/cluster resource holds observed values from the cluster.

ParameterDescription

internalRegistryHostname

Set by the Image Registry Operator, which controls the internalRegistryHostname. It sets the hostname for the default internal image registry. The value must be in hostname[:port] format. For backward compatibility, you can still use the OPENSHIFT_DEFAULT_REGISTRY environment variable, but this setting overrides the environment variable.

externalRegistryHostnames

Set by the Image Registry Operator, provides the external hostnames for the image registry when it is exposed externally. The first value is used in publicDockerImageRepository field in image streams. The values must be in hostname[:port] format.

Configuring image registry settings

You can configure image registry settings by editing the image.config.openshift.io/cluster custom resource (CR). The Machine Config Operator (MCO) watches the image.config.openshift.io/cluster CR for any changes to the registries and reboots the nodes when it detects changes.

Procedure

  1. Edit the image.config.openshift.io/cluster custom resource:

    1. $ oc edit image.config.openshift.io/cluster

    The following is an example image.config.openshift.io/cluster CR:

    1. apiVersion: config.openshift.io/v1
    2. kind: Image (1)
    3. metadata:
    4.   annotations:
    5.     release.openshift.io/create-only: "true"
    6.   creationTimestamp: "2019-05-17T13:44:26Z"
    7.   generation: 1
    8.   name: cluster
    9.   resourceVersion: "8302"
    10.   selfLink: /apis/config.openshift.io/v1/images/cluster
    11.   uid: e34555da-78a9-11e9-b92b-06d6c7da38dc
    12. spec:
    13.   allowedRegistriesForImport: (2)
    14.     - domainName: quay.io
    15.       insecure: false
    16.   additionalTrustedCA: (3)
    17.     name: myconfigmap
    18.   registrySources:(4)
    19.     allowedRegistries:
    20.     - example.com
    21.     - quay.io
    22.     - registry.redhat.io
    23.     - image-registry.openshift-image-registry.svc:5000
    24.     insecureRegistries:
    25.     - insecure.com
    26. status:
    27.   internalRegistryHostname: image-registry.openshift-image-registry.svc:5000
    1Image: Holds cluster-wide information about how to handle images. The canonical, and only valid name is cluster.
    2allowedRegistriesForImport: Limits the container image registries from which normal users may import images. Set this list to the registries that you trust to contain valid images, and that you want applications to be able to import from. Users with permission to create images or ImageStreamMappings from the API are not affected by this policy. Typically only cluster administrators have the appropriate permissions.
    3additionalTrustedCA: A reference to a config map containing additional certificate authorities (CA) that are trusted during image stream import, pod image pull, openshift-image-registry pullthrough, and builds. The namespace for this config map is openshift-config. The format of the config map is to use the registry hostname as the key, and the PEM certificate as the value, for each additional registry CA to trust.
    4registrySources: Contains configuration that determines whether the container runtime allows or blocks individual registries when accessing images for builds and pods. Either the allowedRegistries parameter or the blockedRegistries parameter can be set, but not both. You can also define whether or not to allow access to insecure registries. This example uses the allowedRegistries parameter, which defines the registries that are allowed to be used. The insecure registry insecure.com is also allowed. The registrySources paramter does not contain configuration for the internal cluster registry.

    When the allowedRegistries parameter is defined, all registries, including the registry.redhat.io and quay.io registries and the default internal image registry, are blocked unless explicitly listed. If you use the parameter, to prevent pod failure, you must add the registry.redhat.io and quay.io registries and the internalRegistryHostname to the allowedRegistries list, because they are required by payload images within your environment. Do not add the registry.redhat.io and quay.io registries to the blockedRegistries list.

    Insecure external registries should be avoided to reduce possible security risks.

  2. To check that the changes are applied, list your nodes:

    1. $ oc get nodes

    Example output

    1. NAME                                       STATUS                     ROLES    AGE   VERSION
    2. ci-ln-j5cd0qt-f76d1-vfj5x-master-0         Ready                         master   98m   v1.19.0+7070803
    3. ci-ln-j5cd0qt-f76d1-vfj5x-master-1         Ready,SchedulingDisabled      master   99m   v1.19.0+7070803
    4. ci-ln-j5cd0qt-f76d1-vfj5x-master-2         Ready                         master   98m   v1.19.0+7070803
    5. ci-ln-j5cd0qt-f76d1-vfj5x-worker-b-nsnd4   Ready                         worker   90m   v1.19.0+7070803
    6. ci-ln-j5cd0qt-f76d1-vfj5x-worker-c-5z2gz   NotReady,SchedulingDisabled   worker   90m   v1.19.0+7070803
    7. ci-ln-j5cd0qt-f76d1-vfj5x-worker-d-stsjv   Ready                         worker   90m   v1.19.0+7070803

Adding specific registries

You can add a list of registries that are permitted for image pull and push actions by editing the image.config.openshift.io/cluster custom resource (CR). OKD applies the changes to this CR to all nodes in the cluster.

When pulling or pushing images, the container runtime searches the registries listed under the registrySources parameter in the image.config.openshift.io/cluster CR. If you created a list of registries under the allowedRegistries parameter, the container runtime searches only those registries. Registries not in the list are blocked.

When the allowedRegistries parameter is defined, all registries, including the registry.redhat.io and quay.io registries and the default internal image registry, are blocked unless explicitly listed. If you use the parameter, to prevent pod failure, add the registry.redhat.io and quay.io registries and the internalRegistryHostname to the allowedRegistries list, as they are required by payload images within your environment. For disconnected clusters, mirror registries should also be added.

Procedure

  1. Edit the image.config.openshift.io/cluster CR:

    1. $ oc edit image.config.openshift.io/cluster

    The following is an example image.config.openshift.io/cluster CR with an allowed list:

    1. apiVersion: config.openshift.io/v1
    2. kind: Image
    3. metadata:
    4.   annotations:
    5.     release.openshift.io/create-only: "true"
    6.   creationTimestamp: "2019-05-17T13:44:26Z"
    7.   generation: 1
    8.   name: cluster
    9.   resourceVersion: "8302"
    10.   selfLink: /apis/config.openshift.io/v1/images/cluster
    11.   uid: e34555da-78a9-11e9-b92b-06d6c7da38dc
    12. spec:
    13.   registrySources: (1)
    14.     allowedRegistries: (2)
    15.     - example.com
    16.     - quay.io
    17.     - registry.redhat.io
    18. status:
    19.   internalRegistryHostname: image-registry.openshift-image-registry.svc:5000
    1registrySources: Contains configurations that determine how the container runtime should treat individual registries when accessing images for builds and pods. It does not contain configuration for the internal cluster registry.
    2allowedRegistries: Registries to use for image pull and push actions. All other registries are blocked.

    Either the allowedRegistries parameter or the blockedRegistries parameter can be set, but not both.

    The Machine Config Operator (MCO) watches the image.config.openshift.io/cluster CR for any changes to registries and reboots the nodes when it detects changes. Changes to the allowed registries creates or updates the image signature policy in the /host/etc/containers/policy.json file on each node.

  2. To check that the registries have been added to the policy file, use the following command on a node:

    1. $ cat /host/etc/containers/policy.json

    The following policy indicates that only images from the example.com, quay.io, and registry.redhat.io registries are permitted for image pulls and pushes:

    Example image signature policy file

    1. {
    2.    "default":[
    3.       {
    4.          "type":"reject"
    5.       }
    6.    ],
    7.    "transports":{
    8.       "atomic":{
    9.          "example.com":[
    10.             {
    11.                "type":"insecureAcceptAnything"
    12.             }
    13.          ],
    14.          "image-registry.openshift-image-registry.svc:5000":[
    15.             {
    16.                "type":"insecureAcceptAnything"
    17.             }
    18.          ],
    19.          "insecure.com":[
    20.             {
    21.                "type":"insecureAcceptAnything"
    22.             }
    23.          ],
    24.          "quay.io":[
    25.             {
    26.                "type":"insecureAcceptAnything"
    27.             }
    28.          ],
    29.          "reg4.io/myrepo/myapp:latest":[
    30.             {
    31.                "type":"insecureAcceptAnything"
    32.             }
    33.          ],
    34.          "registry.redhat.io":[
    35.             {
    36.                "type":"insecureAcceptAnything"
    37.             }
    38.          ]
    39.       },
    40.       "docker":{
    41.          "example.com":[
    42.             {
    43.                "type":"insecureAcceptAnything"
    44.             }
    45.          ],
    46.          "image-registry.openshift-image-registry.svc:5000":[
    47.             {
    48.                "type":"insecureAcceptAnything"
    49.             }
    50.          ],
    51.          "insecure.com":[
    52.             {
    53.                "type":"insecureAcceptAnything"
    54.             }
    55.          ],
    56.          "quay.io":[
    57.             {
    58.                "type":"insecureAcceptAnything"
    59.             }
    60.          ],
    61.          "reg4.io/myrepo/myapp:latest":[
    62.             {
    63.                "type":"insecureAcceptAnything"
    64.             }
    65.          ],
    66.          "registry.redhat.io":[
    67.             {
    68.                "type":"insecureAcceptAnything"
    69.             }
    70.          ]
    71.       },
    72.       "docker-daemon":{
    73.          "":[
    74.             {
    75.                "type":"insecureAcceptAnything"
    76.             }
    77.          ]
    78.       }
    79.    }
    80. }

If your cluster uses the registrySources.insecureRegistries parameter, ensure that any insecure registries are included in the allowed list.

For example:

  1. spec:
  2.   registrySources:
  3.     insecureRegistries:
  4.     - insecure.com
  5.     allowedRegistries:
  6.     - example.com
  7.     - quay.io
  8.     - registry.redhat.io
  9.     - insecure.com
  10.     - image-registry.openshift-image-registry.svc:5000

Blocking specific registries

You can block any registry by editing the image.config.openshift.io/cluster custom resource (CR). OKD applies the changes to this CR to all nodes in the cluster.

When pulling or pushing images, the container runtime searches the registries listed under the registrySources parameter in the image.config.openshift.io/cluster CR. If you created a list of registries under the blockedRegistries parameter, the container runtime does not search those registries. All other registries are allowed.

To prevent pod failure, do not add the registry.redhat.io and quay.io registries to the blockedRegistries list, as they are required by payload images within your environment.

Procedure

  1. Edit the image.config.openshift.io/cluster CR:

    1. $ oc edit image.config.openshift.io/cluster

    The following is an example image.config.openshift.io/cluster CR with a blocked list:

    1. apiVersion: config.openshift.io/v1
    2. kind: Image
    3. metadata:
    4.   annotations:
    5.     release.openshift.io/create-only: "true"
    6.   creationTimestamp: "2019-05-17T13:44:26Z"
    7.   generation: 1
    8.   name: cluster
    9.   resourceVersion: "8302"
    10.   selfLink: /apis/config.openshift.io/v1/images/cluster
    11.   uid: e34555da-78a9-11e9-b92b-06d6c7da38dc
    12. spec:
    13.   registrySources: (1)
    14.     blockedRegistries: (2)
    15.     - untrusted.com
    16. status:
    17.   internalRegistryHostname: image-registry.openshift-image-registry.svc:5000
    1registrySources: Contains configurations that determine how the container runtime should treat individual registries when accessing images for builds and pods. It does not contain configuration for the internal cluster registry.
    2Specify registries that should not be used for image pull and push actions. All other registries are allowed.

    Either the blockedRegistries registry or the allowedRegistries registry can be set, but not both.

    The Machine Config Operator (MCO) watches the image.config.openshift.io/cluster CR for any changes to registries and reboots the nodes when it detects changes. Changes to the blocked registries appear in the /etc/containers/registries.conf file on each node.

  2. To check that the registries have been added to the policy file, use the following command on a node:

    1. $ cat /host/etc/containers/registries.conf

    The following example indicates that images from the untrusted.com registry are prevented for image pulls and pushes:

    Example output

    1. unqualified-search-registries = ["registry.access.redhat.com", "docker.io"]
    3. [[registry]]
    4.   prefix = ""
    5.   location = "untrusted.com"
    6.   blocked = true

Allowing insecure registries

You can add insecure registries by editing the image.config.openshift.io/cluster custom resource (CR). OKD applies the changes to this CR to all nodes in the cluster.

Registries that do not use valid SSL certificates or do not require HTTPS connections are considered insecure.

Insecure external registries should be avoided to reduce possible security risks.

Procedure

  1. Edit the image.config.openshift.io/cluster CR:

    1. $ oc edit image.config.openshift.io/cluster

    The following is an example image.config.openshift.io/cluster CR with an insecure registries list:

    1. apiVersion: config.openshift.io/v1
    2. kind: Image
    3. metadata:
    4.   annotations:
    5.     release.openshift.io/create-only: "true"
    6.   creationTimestamp: "2019-05-17T13:44:26Z"
    7.   generation: 1
    8.   name: cluster
    9.   resourceVersion: "8302"
    10.   selfLink: /apis/config.openshift.io/v1/images/cluster
    11.   uid: e34555da-78a9-11e9-b92b-06d6c7da38dc
    12. spec:
    13.   registrySources: (1)
    14.     insecureRegistries: (2)
    15.     - insecure.com
    16.     allowedRegistries:
    17.     - example.com
    18.     - quay.io
    19.     - registry.redhat.io
    20.     - insecure.com (3)
    21.     - reg4.io/myrepo/myapp:latest
    22.     - image-registry.openshift-image-registry.svc:5000
    23. status:
    24.   internalRegistryHostname: image-registry.openshift-image-registry.svc:5000
    1Contains configurations that determine how the container runtime should treat individual registries when accessing images for builds and pods. It does not contain configuration for the internal cluster registry.
    2Specify an insecure registry.
    3Ensure that any insecure registries are included in the allowedRegistries list.

    When the allowedRegistries parameter is defined, all registries, including the registry.redhat.io and quay.io registries and the default internal image registry, are blocked unless explicitly listed. If you use the parameter, to prevent pod failure, add all registries including the registry.redhat.io and quay.io registries and the internalRegistryHostname to the allowedRegistries list, as they are required by payload images within your environment. For disconnected clusters, mirror registries should also be added.

    The Machine Config Operator (MCO) watches the image.config.openshift.io/cluster CR for any changes to registries and reboots the nodes when it detects changes. Changes to the insecure and blocked registries appear in the /etc/containers/registries.conf file on each node.

  2. To check that the registries have been added to the policy file, use the following command on a node:

    1. $ cat /host/etc/containers/registries.conf

    The following example indicates that images from the insecure.com registry is insecure and is allowed for image pulls and pushes.

    Example output

    1. unqualified-search-registries = ["registry.access.redhat.com", "docker.io"]
    3. [[registry]]
    4.   prefix = ""
    5.   location = "insecure.com"
    6.   insecure = true

Configuring additional trust stores for image registry access

The image.config.openshift.io/cluster custom resource can contain a reference to a config map that contains additional certificate authorities to be trusted during image registry access.

Prerequisites

  • The certificate authorities (CA) must be PEM-encoded.

Procedure

You can create a config map in the openshift-config namespace and use its name in AdditionalTrustedCA in the image.config.openshift.io custom resource to provide additional CAs that should be trusted when contacting external registries.

The config map key is the hostname of a registry with the port for which this CA is to be trusted, and the base64-encoded certificate is the value, for each additional registry CA to trust.

Image registry CA config map example

  1. apiVersion: v1
  2. kind: ConfigMap
  3. metadata:
  4.   name: my-registry-ca
  5. data:
  6.   registry.example.com: |
  7.     -----BEGIN CERTIFICATE-----
  8.     ...
  9.     -----END CERTIFICATE-----
  10.   registry-with-port.example.com..5000: | (1)
  11.     -----BEGIN CERTIFICATE-----
  12.     ...
  13.     -----END CERTIFICATE-----
1If the registry has the port, such as registry-with-port.example.com:5000, : should be replaced with ...

You can configure additional CAs with the following procedure.

  1. To configure an additional CA:

    1. $ oc create configmap registry-config --from-file=<external_registry_address>=ca.crt -n openshift-config
    1. $ oc edit image.config.openshift.io cluster
    1. spec:
    2.   additionalTrustedCA:
    3.     name: registry-config

Configuring image registry repository mirroring

Setting up container registry repository mirroring enables you to do the following:

  • Configure your OKD cluster to redirect requests to pull images from a repository on a source image registry and have it resolved by a repository on a mirrored image registry.

  • Identify multiple mirrored repositories for each target repository, to make sure that if one mirror is down, another can be used.

The attributes of repository mirroring in OKD include:

  • Image pulls are resilient to registry downtimes.

  • Clusters in restricted networks can pull images from critical locations, such as quay.io, and have registries behind a company firewall provide the requested images.

  • A particular order of registries is tried when an image pull request is made, with the permanent registry typically being the last one tried.

  • The mirror information you enter is added to the /etc/containers/registries.conf file on every node in the OKD cluster.

  • When a node makes a request for an image from the source repository, it tries each mirrored repository in turn until it finds the requested content. If all mirrors fail, the cluster tries the source repository. If successful, the image is pulled to the node.

Setting up repository mirroring can be done in the following ways:

  • At OKD installation:

    By pulling container images needed by OKD and then bringing those images behind your company’s firewall, you can install OKD into a datacenter that is in a restricted network.

  • After OKD installation:

    Even if you don’t configure mirroring during OKD installation, you can do so later using the ImageContentSourcePolicy object.

The following procedure provides a post-installation mirror configuration, where you create an ImageContentSourcePolicy object that identifies:

  • The source of the container image repository you want to mirror.

  • A separate entry for each mirror repository you want to offer the content requested from the source repository.

You can only configure global pull secrets for clusters that have an ImageContentSourcePolicy object. You cannot add a pull secret to a project.

Prerequisites

  • Access to the cluster as a user with the cluster-admin role.

Procedure

  1. Configure mirrored repositories, by either:

    • Setting up a mirrored repository with Red Hat Quay, as described in Red Hat Quay Repository Mirroring. Using Red Hat Quay allows you to copy images from one repository to another and also automatically sync those repositories repeatedly over time.

    • Using a tool such as skopeo to copy images manually from the source directory to the mirrored repository.

      For example, after installing the skopeo RPM package on a Red Hat Enterprise Linux (RHEL) 7 or RHEL 8 system, use the skopeo command as shown in this example:

      1. $ skopeo copy \
      2. docker://registry.access.redhat.com/ubi8/ubi-minimal@sha256:5cfbaf45ca96806917830c183e9f37df2e913b187adb32e89fd83fa455ebaa6 \
      3. docker://example.io/example/ubi-minimal

      In this example, you have a container image registry that is named example.io with an image repository named example to which you want to copy the ubi8/ubi-minimal image from registry.access.redhat.com. After you create the registry, you can configure your OKD cluster to redirect requests made of the source repository to the mirrored repository.

  2. Log in to your OKD cluster.

  3. Create an ImageContentSourcePolicy file (for example, registryrepomirror.yaml), replacing the source and mirrors with your own registry and repository pairs and images:

    1. apiVersion: operator.openshift.io/v1alpha1
    2. kind: ImageContentSourcePolicy
    3. metadata:
    4.   name: ubi8repo
    5. spec:
    6.   repositoryDigestMirrors:
    7.   - mirrors:
    8.     - example.io/example/ubi-minimal (1)
    9.     source: registry.access.redhat.com/ubi8/ubi-minimal (2)
    10.   - mirrors:
    11.     - example.com/example/ubi-minimal
    12.     source: registry.access.redhat.com/ubi8/ubi-minimal
    13.   - mirrors:
    14.     - mirror.example.com/redhat
    15.     source: registry.redhat.io/openshift4 (3)
    1Indicates the name of the image registry and repository.
    2Indicates the registry and repository containing the content that is mirrored.
    3You can configure a namespace inside a registry to use any image in that namespace. If you use a registry domain as a source, the ImageContentSourcePolicy resource is applied to all repositories from the registry.

  4. Create the new ImageContentSourcePolicy object:

    1. $ oc create -f registryrepomirror.yaml

    After the ImageContentSourcePolicy object is created, the new settings are deployed to each node and the cluster starts using the mirrored repository for requests to the source repository.

  5. To check that the mirrored configuration settings, are applied, do the following on one of the nodes.

    1. List your nodes:

      1. $ oc get node

      Example output

      1. NAME                           STATUS                     ROLES    AGE  VERSION
      2. ip-10-0-137-44.ec2.internal    Ready                      worker   7m   v1.19.0
      3. ip-10-0-138-148.ec2.internal   Ready                      master   11m  v1.19.0
      4. ip-10-0-139-122.ec2.internal   Ready                      master   11m  v1.19.0
      5. ip-10-0-147-35.ec2.internal    Ready,SchedulingDisabled   worker   7m   v1.19.0
      6. ip-10-0-153-12.ec2.internal    Ready                      worker   7m   v1.19.0
      7. ip-10-0-154-10.ec2.internal    Ready                      master   11m  v1.19.0

      You can see that scheduling on each worker node is disabled as the change is being applied.

    2. Start the debugging process to access the node:

      1. $ oc debug node/ip-10-0-147-35.ec2.internal

      Example output

      1. Starting pod/ip-10-0-147-35ec2internal-debug ...
      2. To use host binaries, run `chroot /host`

    3. Access the node’s files:

      1. sh-4.2# chroot /host

    4. Check the /etc/containers/registries.conf file to make sure the changes were made:

      1. sh-4.2# cat /etc/containers/registries.conf

      Example output

      1. unqualified-search-registries = ["registry.access.redhat.com", "docker.io"]
      2. [[registry]]
      3.   location = "registry.access.redhat.com/ubi8/"
      4.   insecure = false
      5.   blocked = false
      6.   mirror-by-digest-only = true
      7.   prefix = ""
      9.   [[registry.mirror]]
      10.     location = "example.io/example/ubi8-minimal"
      11.     insecure = false
      13.   [[registry.mirror]]
      14.     location = "example.com/example/ubi8-minimal"
      15.     insecure = false

    5. Pull an image digest to the node from the source and check if it is resolved by the mirror. ImageContentSourcePolicy objects support image digests only, not image tags.

      1. sh-4.2# podman pull --log-level=debug registry.access.redhat.com/ubi8/ubi-minimal@sha256:5cfbaf45ca96806917830c183e9f37df2e913b187adb32e89fd83fa455ebaa6

Troubleshooting repository mirroring

If the repository mirroring procedure does not work as described, use the following information about how repository mirroring works to help troubleshoot the problem.

  • The first working mirror is used to supply the pulled image.

  • The main registry is only used if no other mirror works.

  • From the system context, the Insecure flags are used as fallback.

  • The format of the /etc/containers/registries.conf file has changed recently. It is now version 2 and in TOML format.

Additional resources

For more information about global pull secrets, see Updating the global cluster pull secret.