Skip to content

[release-4.19] NE-2376: Remove restriction of unmanaged x-k8s.io#30719

Open
openshift-cherrypick-robot wants to merge 1 commit into
openshift:release-4.19from
openshift-cherrypick-robot:cherry-pick-30658-to-release-4.19
Open

[release-4.19] NE-2376: Remove restriction of unmanaged x-k8s.io#30719
openshift-cherrypick-robot wants to merge 1 commit into
openshift:release-4.19from
openshift-cherrypick-robot:cherry-pick-30658-to-release-4.19

Conversation

@openshift-cherrypick-robot
Copy link
Copy Markdown

@openshift-cherrypick-robot openshift-cherrypick-robot commented Jan 22, 2026

This is an automated cherry-pick of #30658

/assign rikatz

@rikatz
NE-2376: Remove restriction of unmanaged x-k8s.io
63ff701 
Previously, cluster-ingress-operator would manage and block any
    updates to CRDs that were from group gateway.networking.x-k8s.io.

    After some analysis we identified that OSSM/Istio does filter these
    resources in case it does not have a flag to enable alpha APIs, which means
    it is safe to allow users to deploy these CRDs.

    This way, this change removes any restriction on x-k8s.io group,
    and removes any further reconciliation from CIO on x-k8s.io group.

Signed-off-by: Ricardo Pchevuzinske Katz <katz@redhat.com>
@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Jan 22, 2026
Merged
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Jan 22, 2026 •
edited by openshift-ci Bot
Loading

@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: NE-2376

Details

In response to this:

This is an automated cherry-pick of #30658

/assign rikatz

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 alebedev87 and candita January 22, 2026 22:10
@rikatz
Copy link
Copy Markdown
Member

rikatz commented Jan 22, 2026

/lgtm
/approve
/cc @Miciah
/hold

@openshift-ci openshift-ci Bot requested a review from Miciah January 22, 2026 22:11
@openshift-ci openshift-ci Bot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. lgtm Indicates that a PR is ready to be merged. labels Jan 22, 2026
@Miciah
Copy link
Copy Markdown
Contributor

Miciah commented Jan 22, 2026

/approve

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jan 22, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Miciah, openshift-cherrypick-robot, rikatz

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 22, 2026
@Miciah Miciah mentioned this pull request Jan 22, 2026
Merged
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jan 23, 2026

@openshift-cherrypick-robot: The following tests 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-metal-ipi-ovn-ipv6 63ff701 link true /test e2e-metal-ipi-ovn-ipv6
ci/prow/verify 63ff701 link true /test verify
ci/prow/e2e-aws-ovn-edge-zones 63ff701 link true /test e2e-aws-ovn-edge-zones

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.

@knobunc
Copy link
Copy Markdown
Contributor

knobunc commented Jan 23, 2026

/label cherry-pick-approved

@openshift-ci openshift-ci Bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Jan 23, 2026
@openshift-bot
Copy link
Copy Markdown
Contributor

openshift-bot commented Apr 24, 2026

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci Bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 24, 2026
@candita
Copy link
Copy Markdown
Contributor

candita commented Apr 24, 2026

/remove-lifecycle stale

@rikatz this one has CI verify failures as well.

@openshift-ci openshift-ci Bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@alebedev87 alebedev87 Awaiting requested review from alebedev87

@candita candita Awaiting requested review from candita

@Miciah Miciah Awaiting requested review from Miciah

Assignees

@rikatz rikatz

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

7 participants

@openshift-cherrypick-robot @openshift-ci-robot @rikatz @Miciah @knobunc @openshift-bot @candita