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.

Sign up for GitHub

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

Jump to bottom

Document CAPA usage of public IPs for AWS #35

Closed
a13x5 opened this issue Feb 3, 2025 · 0 comments · Fixed by #69
Closed

Document CAPA usage of public IPs for AWS #35

a13x5 opened this issue Feb 3, 2025 · 0 comments · Fixed by #69
Assignees
@augustmckendrick
Labels
documentation Improvements or additions to documentation enhancement New feature or request

Comments

@a13x5
Copy link

a13x5 commented Feb 3, 2025

Currently there is a requirement for 3 public IPs for each cluster (due to 3 AZ NAT gateways) when deploying a cluster.
The default EC2-VPC Elastic IPs quota is 5 and may raise unpleasant surprise when deploying more that 1 cluster in a single region.

This requirements must be explicitly mentioned in the docs, presuming that user has limited experience with AWS. Also we must explain the need for 3 public IPs.
@randybias randybias added documentation Improvements or additions to documentation enhancement New feature or request labels Feb 4, 2025
@augustmckendrick augustmckendrick linked a pull request Feb 9, 2025 that will close this issue
Added information on requesting additional IPs in AWS #69
Merged
@github-project-automation github-project-automation bot moved this to Todo in k0rdent Feb 12, 2025
@github-project-automation github-project-automation bot moved this from Todo to Done in k0rdent Feb 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@augustmckendrick augustmckendrick

Labels
documentation Improvements or additions to documentation enhancement New feature or request
Projects
k0rdent
Status: Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Added information on requesting additional IPs in AWS augustmckendrick/newdocs
4 participants
@randybias @jjainschigg-r @a13x5 @augustmckendrick