Skip to content

AGENT-1426: Use localhost for registry domain in interactive flow#645

Open
danielerez wants to merge 1 commit intoopenshift:masterfrom
danielerez:support-interactive-flow-localhost-registry
Open

AGENT-1426: Use localhost for registry domain in interactive flow#645
danielerez wants to merge 1 commit intoopenshift:masterfrom
danielerez:support-interactive-flow-localhost-registry

Conversation

@danielerez
Copy link
Contributor

When EnableInteractiveFlow is enabled, configure registry mirrors and oc-mirror output to use localhost instead of the default registry domain. This is needed to avoid any suprious entries in registries.conf file.

Changes:

  • Update generateRegistries to accept enableInteractiveFlow parameter
  • Use localhost when interactive flow is enabled for registry mirrors
  • Update copyOutputYamls to use localhost registry domain in interactive flow
  • Add swag import for boolean value handling

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jan 28, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 28, 2026

@danielerez: This pull request references AGENT-1426 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.22.0" version, but no target version was set.

Details

In response to this:

When EnableInteractiveFlow is enabled, configure registry mirrors and oc-mirror output to use localhost instead of the default registry domain. This is needed to avoid any suprious entries in registries.conf file.

Changes:

  • Update generateRegistries to accept enableInteractiveFlow parameter
  • Use localhost when interactive flow is enabled for registry mirrors
  • Update copyOutputYamls to use localhost registry domain in interactive flow
  • Add swag import for boolean value handling

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.

@openshift-ci openshift-ci bot requested review from gamli75 and jhernand January 28, 2026 09:52
@openshift-ci
Copy link

openshift-ci bot commented Jan 28, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: danielerez

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

The pull request process is described here

Details 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 Jan 28, 2026
@danielerez
Copy link
Contributor Author

/retest

1 similar comment
@danielerez
Copy link
Contributor Author

/retest

@danielerez danielerez force-pushed the support-interactive-flow-localhost-registry branch from 8dc40fc to 26d5f6f Compare February 25, 2026 19:00
When EnableInteractiveFlow is enabled, configure registry mirrors and
oc-mirror output to use localhost instead of the default registry domain.
This is needed to avoid any suprious entries in registries.conf file.

Changes:
- Update generateRegistries to accept enableInteractiveFlow parameter
- Use localhost when interactive flow is enabled for registry mirrors
- Update copyOutputYamls to use localhost registry domain in interactive flow
- Add swag import for boolean value handling
@danielerez danielerez force-pushed the support-interactive-flow-localhost-registry branch from 26d5f6f to d0c1259 Compare February 25, 2026 20:56
@danielerez
Copy link
Contributor Author

/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 27, 2026
@andfasano
Copy link
Contributor

@danielerez I'd like to land first openshift/release#75449 (and all of its dependencies) to have a more consolidated ways to test OVE related patches (now that we've got a fully working CI job)

@danielerez
Copy link
Contributor Author

@danielerez I'd like to land first openshift/release#75449 (and all of its dependencies) to have a more consolidated ways to test OVE related patches (now that we've got a fully working CI job)

ack.
we need to handle it in the internalReleaseImagePatcher first anyway. i.e. to ensure "localhost" isn't added twice (by appliance and assisted-service): https://github.com/openshift/assisted-service/blob/3788a410ec344ffd5c10e8ee65f506ee362c4801/internal/ignition/internalreleaseimage_patcher.go#L199

if swag.BoolValue(enableInteractiveFlow) {
r.Mirrors = append(r.Mirrors, sysregistriesv2.Endpoint{
Location: re.ReplaceAllString(m, fmt.Sprintf("%s:%d", "localhost", RegistryPort)),
})
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wondering why a corresponding entry for RegistryPortUpgrade did not need to be added here.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't use that appliance feature

@andfasano
Copy link
Contributor

@danielerez I'd like to land first openshift/release#75449 (and all of its dependencies) to have a more consolidated ways to test OVE related patches (now that we've got a fully working CI job)

ack. we need to handle it in the internalReleaseImagePatcher first anyway. i.e. to ensure "localhost" isn't added twice (by appliance and assisted-service): https://github.com/openshift/assisted-service/blob/3788a410ec344ffd5c10e8ee65f506ee362c4801/internal/ignition/internalreleaseimage_patcher.go#L199

I think it'd safe to handle it just afterwards. We can test it once the CI job will be available

@andfasano
Copy link
Contributor

/pj-rehearse ?

@andfasano
Copy link
Contributor

/test ?

@andfasano
Copy link
Contributor

/test e2e-agent-compact-ipv4-iso-no-registry

1 similar comment
@andfasano
Copy link
Contributor

/test e2e-agent-compact-ipv4-iso-no-registry

@openshift-ci
Copy link

openshift-ci bot commented Mar 13, 2026

@danielerez: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-agent-compact-ipv4-iso-no-registry d0c1259 link false /test e2e-agent-compact-ipv4-iso-no-registry

Full PR test history. Your PR dashboard.

Details

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. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants