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 1990012: Update controller config openapi schema #2702
Bug 1990012: Update controller config openapi schema #2702
Conversation
@JoelSpeed: This pull request references Bugzilla bug 1990012, 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
No GitHub users were found matching the public email listed for the QA contact in Bugzilla (rioliu@redhat.com), skipping review request. 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 kubernetes/test-infra repository. |
e63680e
to
0e99632
Compare
Sinny has been looking at moving our API to openshift/api, so looping her in to take a look. Could you also provide some steps you used to generate this? I tried some time ago to use the generator and wasn't fully successful, and I think recently Sinny also had to do some manual steps to update this. Might be good to have it documented in our hacking doc for future reference. |
Sure, we have a script that runs this for us in MAO, so I originally started by copying that and trying to make it work for your project as I noticed you don't have a script for doing it. The problem I reached was that your machineconfig has a raw extension, currently you have a schema defined within this even though it's not needed, so there's a large diff on the CR, everything else is pretty much ok and as normal You can see the progress I made here JoelSpeed@8769284 Theres a few changes I had to make in |
/test e2e-azure @lobziik built a release image built with this patch. It resolves issues for joining worker nodes in Azure Stack UPI. |
/test e2e-agnostic-upgrade |
/test e2e-agnostic-upgrade Is there anything more we need to do for this? |
/test e2e-agnostic-upgrade |
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.
Upgrade test failures seem unrelated to this PR. Generally lgtm, will give others a chance to take a last look if any concerns.
Thanks Joel for catching this issue and opening up PR!
+1, hopefully we will not have these issues once we finish our work to move MCO API to openshift/api /lgtm |
/retest |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: JoelSpeed, sinnykumari, yuqi-zhang 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 |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
8 similar comments
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
16 similar comments
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
@JoelSpeed: The following tests failed, say
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/test-infra repository. I understand the commands that are listed here. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
6 similar comments
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
@JoelSpeed: All pull requests linked via external trackers have merged: Bugzilla bug 1990012 has been moved to the MODIFIED state. 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 kubernetes/test-infra repository. |
- What I did
I used controller-gen to regenerate the openAPIV3Schema section of this CRD.
This means that it is now up to date and includes all of the latest fields from the objects that are embedded within it.
- How to verify it
Find a field such as
.spec.infra.status.platformStatus.azure.cloudName
which is not currently present in the CRD schema. Observe how this exists in theinfrastructure
resource, but does not exist in the embedded infra in thecontrollerconfig
in clusters today. Try to add this field into thecontrollerconfig
, it will be silently dropped by the API server.Upgrade to this patch, observe how the field now exists and is copied from the main
infrastructure
resource.- Description for the changelog
Update OpenAPI schema for
controllerconfig
CRD