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

Feature Request: Only Provision Two NAT Gateways #921

Closed
andrewbcoyle opened this issue Apr 10, 2023 · 3 comments
Closed

Feature Request: Only Provision Two NAT Gateways #921

andrewbcoyle opened this issue Apr 10, 2023 · 3 comments
Labels

Comments

@andrewbcoyle
Copy link

I would like an option added to provision only two NAT Gateways in a VPC.

The use case is an EKS cluster that spans more than 2 AZ's and has more than 2 private subnets. I want 2 NATs for high availability, but I don;t need more than that (i.e. I don't need one in every AZ if a cluster spans multiple AZs) since cluster networking can route traffic to a NAT in another AZ if needed.

It should be noted that there is an upcharge in intra-AZ traffic, but given the cost of a NAT gateway, I think this use request is valid.

Thoughts?

@github-actions
Copy link

This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

@github-actions github-actions bot added the stale label May 11, 2023
@github-actions
Copy link

This issue was automatically closed because of stale in 10 days

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 21, 2023
@github-actions
Copy link

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 20, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant