-
Notifications
You must be signed in to change notification settings - Fork 38
npep-187: More protocols support #297
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
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Nadia Pinaeva <[email protected]>
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: npinaeva The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
✅ Deploy Preview for kubernetes-sigs-network-policy-api ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
High level looks ok to me plus aligns with what was discussed. /lgtm |
``` | ||
|
||
with the validation like so: | ||
- empty `protocols` list is not allowed |
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.
Clarification: this is having just protocols: but no list
?
with the validation like so: | ||
- empty `protocols` list is not allowed | ||
- at least 1 field for each `protocol` element must be set | ||
- if `namedPort` is set, `protocol` must be unset |
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 think we were thinking to not have namedPort for the first pass?
How do we make progress on this? |
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
Issue: #187
TODO: also reference #247 when we are closer to the API design