-
Notifications
You must be signed in to change notification settings - Fork 40.1k
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
prevent unsetting of nonexistent previous port in kubeapi-load-balancer charm #49033
prevent unsetting of nonexistent previous port in kubeapi-load-balancer charm #49033
Conversation
Hi @wwwtyro. 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 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. I understand the commands that are listed here. |
/assign @Cynerva |
/ok-to-test |
Ah yeah, missed this in the last review. /approve no-issue |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Cynerva, wwwtyro Associated issue requirement bypassed by: Cynerva The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
Automatic merge from submit-queue (batch tested with PRs 48231, 47377, 48797, 49020, 49033) |
What this PR does / why we need it: prevent unsetting of nonexistent previous port in kubeapi-load-balancer charm
Release note: