Skip to content

OCPBUGS-72408: add defaults to allowed registries#651

Open
dusk125 wants to merge 3 commits intoopenshift:mainfrom
dusk125:imagestreamimport
Open

OCPBUGS-72408: add defaults to allowed registries#651
dusk125 wants to merge 3 commits intoopenshift:mainfrom
dusk125:imagestreamimport

Conversation

@dusk125
Copy link

@dusk125 dusk125 commented Feb 20, 2026 •
edited
Loading

This PR provides defaults so that the cluster will continue to function even with the change from allow-all to deny-all introduced here: openshift/openshift-apiserver#607

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 20, 2026
@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Feb 20, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 20, 2026

@dusk125: This pull request references Jira Issue OCPBUGS-72408, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.22.0) matches configured target version for branch (4.22.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @xiuwang

The bug has been updated to refer to the pull request using the external bug tracker.

Details

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

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 20, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dusk125
Once this PR has been reviewed and has the lgtm label, please assign sanchezl for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

@dusk125 dusk125 mentioned this pull request Feb 20, 2026
Open
@dusk125 dusk125 changed the title WIP: OCPBUGS-72408: add defaults to allowed registries OCPBUGS-72408: add defaults to allowed registries Feb 20, 2026
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 20, 2026
@dusk125
Copy link
Author

dusk125 commented Feb 20, 2026

/retest-required

2 similar comments
@dusk125
Copy link
Author

dusk125 commented Feb 23, 2026

/retest-required

@dusk125
Copy link
Author

dusk125 commented Feb 23, 2026

/retest-required

@dusk125
Copy link
Author

dusk125 commented Feb 23, 2026

/label tide/merge-method-squash

@openshift-ci openshift-ci bot added the tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. label Feb 23, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 24, 2026

@dusk125: 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-aws-ovn 68ab437 link true /test e2e-aws-ovn

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.

@dusk125
Copy link
Author

dusk125 commented Feb 25, 2026

/hold
need to ensure this is the path we want to go down

@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 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@xiuwang xiuwang Awaiting requested review from xiuwang

@p0lyn0mial p0lyn0mial Awaiting requested review from p0lyn0mial

@sanchezl sanchezl Awaiting requested review from sanchezl

Assignees

No one assigned

Labels

do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@dusk125 @openshift-ci-robot