-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Bug 2037813: [baremetal] networkConfig field now accepts yaml instead of string value #5545
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 2037813: [baremetal] networkConfig field now accepts yaml instead of string value #5545
Conversation
|
@andfasano: This pull request references Bugzilla bug 2037813, 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 ([email protected]), skipping review request. 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. |
staebler
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.
The current patch allows the user to specify the content of the install-config networkConfig field directly as a yaml object.
Hooray for this!
|
/approve |
bde6afd to
a0a3c22
Compare
|
Unfortunate that we can't allow a string as well, but it appears to me that would be banned by rule 3 of https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/#specifying-a-structural-schema /approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: staebler, zaneb 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 |
You could have two separate fields--one that takes yaml and one that takes a string. The installer would fill out the one that is easier to use internally with the value from the other, if set. The installer would need to validate that if both are set that they are equivalent. |
|
/lgtm Nice improvement. |
|
/hold let's wait for the results of the pending jobs |
|
/test e2e-metal-ipi-ovn-ipv6-required |
The main reason to support both would be so that we don't have to worry about users doing it wrong, so I think having two fields is just giving people twice as many ways to mess up :) |
|
/hold cancel Agree also on just keeping one field for the sake of simplicity |
|
/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. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
5 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. |
a0a3c22 to
e23e547
Compare
|
There was a problem with the |
|
/test verify-vendor |
e23e547 to
cbd51fd
Compare
pkg/types/baremetal/platform.go
Outdated
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.
I guess the plus side of this is that you could accept a string here as well. I don't know if we want to, but you could.
The current patch allows the user to specify the content of the install-config networkConfig field directly as a yaml object. Content validation (for a generic yaml) is now carried on by the install config asset
cbd51fd to
8b3d14d
Compare
|
/lgtm |
|
/hold |
|
/hold cancel /test e2e-metal-ipi-ovn-ipv6-required |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
@andfasano: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
@andfasano: All pull requests linked via external trackers have merged: Bugzilla bug 2037813 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. |
The current patch allows the user to specify the content of the install-config networkConfig field directly as a yaml object. Content validation (for a generic yaml) is now carried on by the install config asset
/label platform/baremetal