-
Notifications
You must be signed in to change notification settings - Fork 0
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
ACM hits Elastic IPs quota on AWS #28
Comments
This should be a requirement from OpenShift IPI installation "Each private subnet requires a NAT Gateway, and each NAT gateway requires a separate elastic IP. " So, 3 for node, 3 for NAT gateway. |
@cdoan1 Not sure where you deduced 3 for nodes + 3 for gateway. The docs says: I deduce this mapping from it: And since we're deploying to 3 avail zones, that is Also the second highlighted sentence says:
Which also supports my finding, because the default limit is 5. Therefore if you install into more than 5 avail zones, you need more than 5 on quota. I don't see anywhere in the docs to specify 1 additional EIP per node or multiply by 2... Where do you read that? |
Hey,
I tried to change the region to "eu-west-2" out of curiosity and expected to see the same result, but the second time the number of resources that was asked was different:
I didn't change the default amount of masters and workers. |
I've tried spinning up a "test" cluster in AWS via ACM. It's a cluster of 1 master node and 3 worker nodes. Just a small one. The provisioning failed, because I was deploying it to a region where the Elastic IPs quota was set to default=5.
Later on we discovered that we have another region in our account with this quota set to 10 so we redo the provisioning to that different region with the same cluster settings. The cluster deployed successfully, though there are only 3 allocated Elastic IPs.
Why it requires the quota to be 6 if it allocates only 3 Elastic IPs?
cc @ipolonsk @idanlv @cdoan1
The text was updated successfully, but these errors were encountered: