-
Notifications
You must be signed in to change notification settings - Fork 431
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
Make NAT Gateway reconcile/delete async #1865
Conversation
Hi @Jont828. Thanks for your PR. I'm waiting for a kubernetes-sigs 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. |
/assign mboersma I'd appreciate feedback on the reconcile/delete logic. I'm curious about if we need to set the subnets at the end of a Reconcile() loop since I don't believe removing it would change any behavior. And btw I'm holding off on refactoring the tests until the reconcile/delete functions are at a good spot. |
azure/services/natgateways/spec.go
Outdated
if !(natGateway.PublicIPAddresses != nil && len(*natGateway.PublicIPAddresses) > 0) { | ||
return "", errors.New("failed to parse PublicIPAddresses") | ||
} | ||
// TODO: do we need to handle NatGateway resources w/ more than one public IP address? |
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.
Could you please open an issue for this? We're treating NAT gateways as if they only had 1 IP in the API but really they can have a list of associated public IPs.
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.
cc @jackfrancis
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 pushed the changes to implement hasPublicIP
instead, which I think gets us around this issue since we search all the public IPs in a NAT gateway.
/ok-to-test |
0ff19f5
to
494e77d
Compare
Please squash commits |
104bd4d
to
717753a
Compare
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.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: CecileRobertMichon 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 |
/lgtm cancel |
5f9aa9f
to
32788e8
Compare
32788e8
to
c17869e
Compare
c17869e
to
154bf95
Compare
/lgtm |
@Jont828: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. |
What type of PR is this?
/kind feature
What this PR does / why we need it: Implementation of an async service for NAT gateways as a follow up for #1610 and #1541.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #1714
Special notes for your reviewer:
Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.
TODOs:
Release note: