-
Notifications
You must be signed in to change notification settings - Fork 462
Bug 1947791: Switch CRDs to v1 #2572
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug 1947791: Switch CRDs to v1 #2572
Conversation
apiextensions.k8s.io/v1beta1 will be deprecated in kube 1.22+ - Updated CRDS to v1 - Ran `crd-schema-gen.mk` make target from https://github.com/openshift/build-machinery-go/
Since, calling controller-gen wasn't helpful here. Updated manually deprecated fields in CRDs based on doc https://kubernetes.io/docs/reference/using-api/deprecation-guide/#customresourcedefinition-v122
|
@sinnykumari: This pull request references Bugzilla bug 1947791, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
Requesting review from QA contact: DetailsIn 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 kubernetes/test-infra repository. |
|
@sttts @rphillips Please review this, thanks! |
|
Verified with spinning up a local cluster with this PR and seems like deprecated APIs related alerts from MCO has been resolved, verified as per bug comment. Also, no more warning messages /retest |
| apiVersion: apiextensions.k8s.io/v1 | ||
| kind: CustomResourceDefinition | ||
| metadata: | ||
| name: containerruntimeconfigs.machineconfiguration.openshift.io |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we have this in openshift/api ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same question as for those below. All *.openshift.io APIs belong into that repo. Otherwise, we are unable to do cross-component API tasks in a consistent way and have no API review either.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
don't think so. Doing quick grep of "containerruntimeconfigs" in openshift/api repo gives no result.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agree and while working on this PR I was thinking of doing a spike in 4.9 and work on moving MCO APIs to openshift/api repo.
|
/retest |
|
MCO logs looks fine for e2e-agnostic-upgrade test, |
yuqi-zhang
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
First pass looks good! I don't see any references remaining to beta APIs, and it looks like the MCO is successful.
Just to make sure of something, because the diffs look somewhat funky, the actual API+verification we do shouldn't change behaviour right? (I see you manually generated some of our subfields like we did before)
Yeah, it shouldn't change any behavior if corresponding behavior hasn't changed in upstream. |
|
/retest |
|
/test e2e-gcp-upgrade |
|
/retest |
|
lgtm |
|
One more try |
|
/test e2e-agnostic-upgrade |
|
/retest |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sinnykumari, yuqi-zhang The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
3 similar comments
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
@sinnykumari: All pull requests linked via external trackers have merged: Bugzilla bug 1947791 has been moved to the MODIFIED state. DetailsIn 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 kubernetes/test-infra repository. |
apiextensions.k8s.io/v1beta1 will be deprecated in kube 1.22+
Updated CRDs and any usage inside MCO from v1beta to v1
Deprecated CRD fields in v1 are at https://kubernetes.io/docs/reference/using-api/deprecation-guide/#customresourcedefinition-v122