Add UnqualifiedSearchRegistries to the Image CR#28152
Add UnqualifiedSearchRegistries to the Image CR#28152mburke5678 merged 1 commit intoopenshift:masterfrom
Conversation
25292cc to
c1e5bc5
Compare
|
The preview will be available shortly at:
|
381597c to
651ab26
Compare
There was a problem hiding this comment.
This is an editorial change for consistency only. No need for QE review.
There was a problem hiding this comment.
This is an editorial change for 4.7 MCO change previously reviewed. No need for QE review.
There was a problem hiding this comment.
This is an editorial change for consistency only. No need for QE review.
There was a problem hiding this comment.
This is an editorial change for consistency only. No need for QE review.
There was a problem hiding this comment.
This is an editorial change for consistency only. No need for QE review.
There was a problem hiding this comment.
QE, please review this new text.
There was a problem hiding this comment.
QE, please review this new text.
|
@sunilcio PTAL. I made several editorial changes to ensure consistency throughout the other modules in the assembly. Please feel free to not review these changes. |
|
@sunilcio PTAL |
|
@mburke5678 thanks, lgtm! |
5fe0c9a to
578c1e4
Compare
There was a problem hiding this comment.
| The Machine Config Operator (MCO) watches the `image.config.openshift.io/cluster` resource for any changes to the registries. When the MCO detects a change, it drains the nodes, applies the change, and uncordons the nodes. After the nodes return to the `Ready` state, if the `containerRuntimeSearchRegistries` parameter is added, the MCO and creates a file in the `/etc/containers/registries.conf.d` directory on each node with the listed registries. The file overrides the default list of unqualified search registries in the `/host/etc/containers/registries.conf` file. There is no way to fall back to the default list of unqualified search registries. | |
| The Machine Config Operator (MCO) watches the `image.config.openshift.io/cluster` resource for any changes to the registries. When the MCO detects a change, it drains the nodes, applies the change, and uncordons the nodes. After the nodes return to the `Ready` state, if the `containerRuntimeSearchRegistries` parameter is added, the MCO creates a file in the `/etc/containers/registries.conf.d` directory on each node with the listed registries. The file overrides the default list of unqualified search registries in the `/host/etc/containers/registries.conf` file. There is no way to fall back to the default list of unqualified search registries. |
There was a problem hiding this comment.
| The `containerRuntimeSearchRegistries` parameter works only with the Podman and CRI-O container engines and the registries in the list can be used only in pod specs, not in builds and image streams. | |
| The `containerRuntimeSearchRegistries` parameter works only with the Podman and CRI-O container engines. The registries in the list can be used only in pod specs, not in builds and image streams. |
There was a problem hiding this comment.
The + markers are currently rendering (line 83 and 88). I'd suggest making this verification step a numbered step, which would fix the rendering issue.
. To check that the registries have been added, use the following command on a node:
578c1e4 to
c62f761
Compare
|
/cherrypick enterprise-4.7 |
|
@mburke5678: new pull request created: #28416 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
https://issues.redhat.com/browse/OSDOCS-1644