Skip to content

Conversation

benluddy
Copy link
Contributor

@benluddy benluddy commented May 6, 2025

ValidatingAdmissionPolicy currently depends on admissionregistration.k8s.io/v1 and the feature gate is always on. The v1beta1 version wasn't meant to be served outside of tech preview clusters.

Resumes the work started in #1687.

@openshift-ci-robot openshift-ci-robot added 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 May 6, 2025
@openshift-ci-robot
Copy link

@benluddy: This pull request references Jira Issue OCPBUGS-55465, which is valid.

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

Requesting review from QA contact:
/cc @wangke19

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

In response to this:

ValidatingAdmissionPolicy currently depends on admissionregistration.k8s.io/v1 and the feature gate is always on. The v1beta1 version wasn't meant to be served outside of tech preview clusters.

Resumes the work started in #1687.

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 wangke19, dinhxuanvu and sanchezl May 6, 2025 18:18
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 6, 2025
@jacobsee
Copy link
Member

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 12, 2025
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD af13d7a and 2 for PR HEAD 6bae557 in total

@benluddy
Copy link
Contributor Author

/hold

We have some platform components depending on this GV by mistake, holding until those are switched over to v1.

@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 May 13, 2025
@benluddy
Copy link
Contributor Author

benluddy commented Jun 4, 2025

Should be okay to unhold after openshift/kubernetes#2290.

ValidatingAdmissionPolicy currently depends on admissionregistration.k8s.io/v1 and the feature gate
is always on. The v1beta1 version wasn't meant to be served outside of tech preview clusters.
@benluddy benluddy force-pushed the stop-serving-admissionregistration-v1beta1 branch from 6bae557 to 0bdba4f Compare June 16, 2025 13:32
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Jun 16, 2025
@benluddy
Copy link
Contributor Author

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 16, 2025
Copy link
Contributor

openshift-ci bot commented Jun 16, 2025

@benluddy: 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-aws-operator-disruptive-single-node 0bdba4f link false /test e2e-aws-operator-disruptive-single-node
ci/prow/e2e-gcp-operator-single-node 0bdba4f link false /test e2e-gcp-operator-single-node

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.

@benluddy
Copy link
Contributor Author

/retest-required

@benluddy
Copy link
Contributor Author

/cc @JoelSpeed

@openshift-ci openshift-ci bot requested a review from JoelSpeed June 17, 2025 14:13
@JoelSpeed
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 17, 2025
Copy link
Contributor

openshift-ci bot commented Jun 17, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: benluddy, jacobsee, JoelSpeed

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-merge-bot openshift-merge-bot bot merged commit 5cc2e26 into openshift:main Jun 17, 2025
15 of 17 checks passed
@openshift-ci-robot
Copy link

@benluddy: Jira Issue OCPBUGS-55465: Some pull requests linked via external trackers have merged:

The following pull requests linked via external trackers have not merged:

These pull request must merge or be unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

Jira Issue OCPBUGS-55465 has not been moved to the MODIFIED state.

In response to this:

ValidatingAdmissionPolicy currently depends on admissionregistration.k8s.io/v1 and the feature gate is always on. The v1beta1 version wasn't meant to be served outside of tech preview clusters.

Resumes the work started in #1687.

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-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-cluster-kube-apiserver-operator
This PR has been included in build ose-cluster-kube-apiserver-operator-container-v4.20.0-202506172140.p0.g5cc2e26.assembly.stream.el9.
All builds following this will include this PR.

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. 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. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants