-
Notifications
You must be signed in to change notification settings - Fork 585
Bug 1756132: Remove incorrect optional tag from new ingress field #446
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 1756132: Remove incorrect optional tag from new ingress field #446
Conversation
|
@ironcladlou: This pull request references Bugzilla bug 1756132, which is invalid:
Comment 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. |
|
/bugzilla refresh |
|
@ironcladlou: This pull request references Bugzilla bug 1756132, 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. 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. |
| // scope indicates the scope at which the load balancer is exposed. | ||
| // Possible values are "External" and "Internal". The default is | ||
| // "External". | ||
| // +optional |
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.
Looks reasonable to me, but we need clarification from @deads2k regarding https://github.com/openshift/api/pull/312/files#r294390499.
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.
Since the package default is Optional, does this need to be explicitly required?
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 marked this explicitly required and moved the defaulting docs up to the actual point of defaulting (the optional loadBalancer field).
403dbc8 to
13275fd
Compare
`loadBalancer` is a new field that contains `scope`, and `loadBalancer` is optional (correct). However, `loadBalancer.scope` _should_ be required. This commit fixes that.
13275fd to
9c9a7b1
Compare
|
/bugzilla refresh |
|
@knobunc: This pull request references Bugzilla bug 1756132, which is valid. 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. |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ironcladlou, sttts 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 |
|
@ironcladlou: All pull requests linked via external trackers have merged. Bugzilla bug 1756132 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. |
loadBalanceris a new field that containsscope, andloadBalancerisoptional (correct). However,
loadBalancer.scopeshould be required. Thiscommit fixes that.