Skip to content

[release-4.18] MGMT-19545: add optional release registry field to the IBI installation config #9738

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: release-4.18
Choose a base branch
from

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #9394

/assign mresvanis

This change adds the optional `ReleaseRegistry` field in the IBI installation
config. This field is used as a replacement for the seed release registry in the
seed cluster's image pull-specs, when the seed container image is generated in
a disconnected SNO (i.e. with mirror registries configured).

Signed-off-by: Michail Resvanis <[email protected]>
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented May 22, 2025

@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: MGMT-19545

In response to this:

This is an automated cherry-pick of #9394

/assign mresvanis

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 openshift-eng/jira-lifecycle-plugin repository.

@mresvanis
Copy link
Contributor

/cc @tsorya @jc-rh @eranco74

@openshift-ci openshift-ci bot requested review from eranco74, jc-rh, tsorya and javipolo May 22, 2025 08:26
@tsorya
Copy link
Contributor

tsorya commented May 22, 2025

/approve

Copy link
Contributor

openshift-ci bot commented May 22, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tsorya

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 22, 2025
Copy link
Contributor

openshift-ci bot commented May 22, 2025

@openshift-cherrypick-robot: all tests passed!

Full PR test history. Your PR dashboard.

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-sigs/prow repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants