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
Update code comment for NetworkPolicyPeer #89018
Conversation
Hi @abhiraut. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
/sig network |
This PR may require API review. If so, when the changes are ready, complete the pre-review checklist and request an API review. Status of requested reviews is tracked in the API Review project. |
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.
/ok-to-test
@dcbw probably does not require an API review? |
This is going to fail CI - it needs files regenerated. That said, it's a trivial change so: /approve Once you generate files and re-push, we can lgtm |
NetworkPolicyPeer in types has an outdated comment from the times when it only supported ingress rules. Update the comment to reflect the current usage of the field.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: abhiraut, thockin 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 |
/lgtm |
NetworkPolicyPeer in types has an outdated comment from the times when it only supported
ingress rules. Update the comment to reflect the current usage of the field.
/kind cleanup
Does this PR introduce a user-facing change?: