init all not inited vpc nat gw after k8s cluster restarted #3261
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of this PR
Examples of user facing changes:
fix nat gw pod may not inited all its nats after reboot all the whole k8s cluster
Which issue(s) this PR fixes:
Fixes #(issue-number)
WHAT
🤖 Generated by Copilot at ece016a
This pull request adds support for VPC NAT gateways, a new feature that enables outbound connectivity for multiple VPCs in the same cluster. It modifies
controller.go
to initialize the VPC NAT gateways and adds a new functionc.initVpcNatGw()
invpc_nat_gateway.go
to set up the iptables and routes for the gateways.🤖 Generated by Copilot at ece016a
HOW
🤖 Generated by Copilot at ece016a