Skip to content
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

init all not inited vpc nat gw after k8s cluster restarted #3261

Closed

Conversation

bobz965
Copy link
Collaborator

@bobz965 bobz965 commented Sep 26, 2023

What type of this PR

Examples of user facing changes:

  • Bug fixes

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 function c.initVpcNatGw() in vpc_nat_gateway.go to set up the iptables and routes for the gateways.

🤖 Generated by Copilot at ece016a

New feature added
VPC NAT gateways for
Outbound traffic flow

HOW

🤖 Generated by Copilot at ece016a

  • Initialize VPC NAT gateways by adding a new function and calling it before load balancer feature check (link, link)

@bobz965 bobz965 force-pushed the fix-nat-recover-after-node-restart branch from ece016a to 8db2bad Compare September 26, 2023 10:10
@bobz965 bobz965 changed the title init all not inited vpc nat gw after restarted init all not inited vpc nat gw after k8s cluster restarted Sep 26, 2023
@bobz965 bobz965 force-pushed the fix-nat-recover-after-node-restart branch from 8db2bad to d482b6c Compare September 26, 2023 10:12
@bobz965 bobz965 force-pushed the fix-nat-recover-after-node-restart branch from d482b6c to 37214f2 Compare September 27, 2023 07:06
Copy link
Contributor

PRs go stale after 60d of inactivity. Please comment or re-open the PR if you are still working on this PR.

@bobz965 bobz965 closed this Nov 30, 2023
@bobz965 bobz965 deleted the fix-nat-recover-after-node-restart branch December 23, 2023 06:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant