api CNTRLPLANE-72: remove RoleBindingRestriction CRD from payload

so that it can be managed by the cluster-authentication-operator instead of cluster-version-operator. This enables the cluster-authentication-operator to remove the CRD from the cluster when intentionally taking down the OpenShift OAuth stack.

Jan 09 '25 14:01 everettraven

Skipping CI for Draft Pull Request. If you want CI signal for your change, please convert it to an actual PR. You can still manually trigger a test run with /test all

Jan 09 '25 14:01 openshift-ci[bot]

Hello @everettraven! Some important instructions when contributing to openshift/api: API design plays an important part in the user experience of OpenShift and as such API PRs are subject to a high level of scrutiny to ensure they follow our best practices. If you haven't already done so, please review the OpenShift API Conventions and ensure that your proposed changes are compliant. Following these conventions will help expedite the api review process for your PR.

Jan 09 '25 14:01 openshift-ci[bot]

This needs to wait until we have the changes in place on the cluster-authentication-operator to start managing the CRD.

/hold

Jan 09 '25 18:01 everettraven

@everettraven: This pull request references CNTRLPLANE-72 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 story to target the "4.19.0" version, but no target version was set.

In response to this:

so that it can be managed by the cluster-authentication-operator instead of cluster-version-operator. This enables the cluster-authentication-operator to remove the CRD from the cluster when OIDC authentication is configured.

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.

Jan 29 '25 20:01 openshift-ci-robot

@everettraven: This pull request references CNTRLPLANE-72 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 story to target the "4.19.0" version, but no target version was set.

In response to this:

so that it can be managed by the cluster-authentication-operator instead of cluster-version-operator. This enables the cluster-authentication-operator to remove the CRD from the cluster when intentionally taking down the OpenShift OAuth stack.

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.

Jan 29 '25 20:01 openshift-ci-robot

/retest-required

Jan 30 '25 18:01 everettraven

/lgtm

Feb 07 '25 14:02 liouk

/retest

Feb 28 '25 15:02 everettraven

https://github.com/openshift/cluster-authentication-operator/pull/748 and https://github.com/openshift/installer/pull/9424 have merged. This should be good to go as long as tests are happy.

/hold cancel

Feb 28 '25 15:02 everettraven

cc @JoelSpeed for whenever you have time to take a look.

This is part of moving the management of the RoleBindingRestriction CRD to the cluster-authentication-operator. Outlined in https://github.com/openshift/enhancements/pull/1726

Feb 28 '25 15:02 everettraven

/approve