Closed backstreetkiwi closed 2 days ago
Is this a limitation that'll be solved by using native Kubernetes?
Is this a limitation that'll be solved by using native Kubernetes?
@lfrancke This applies to the non-managed clusters which we still need. On the other hand, we haven't hit the limit of elastic IPs (5) so far as Jenkins only runs 4 of these builds in parallel anyway. We might want to keep this task with a loooow priority.
We can easily request a limit increase as well I assume. Just ask me or @razvan to contact support. I've done it in the past and it was painless.
Okay, so you say "AWS is painless"... well... So please decide if you want to drop the ticket or lower the priority. thx
Looks like this is no longer an issue, right, @lfrancke , @Jimvin ?
Agreed
In our AWS clusters, we have a VPC, a public subnet and a NAT gateway with an elastic IP in each Stackable/T2 cluster. As the number of EIPs (elastic IPs) is limited to 5, this might be a limiting factor in the future.
In this article, AWS describes a solution that might be worth having a look at: https://aws.amazon.com/blogs/networking-and-content-delivery/creating-a-single-internet-exit-point-from-multiple-vpcs-using-aws-transit-gateway/