Validate CloudNAT and Woker configuration in shoot spec. #417
Labels
area/networking
Networking related
kind/enhancement
Enhancement, improvement, extension
lifecycle/stale
Nobody worked on this for 6 months (will further age)
platform/gcp
Google cloud platform/infrastructure
How to categorize this issue?
/area networking
/kind enhancement
/platform gcp
What would you like to be added:
Currently I can specify a CloudNat with min ports per VM and a list of manual NAT IP addresses.
I can break the shoot if I specify more nodes in the worker group as are supported by the CloudNAT configuration.
The calculation for the maximum number of allowed nodes with a specific port range per VM is described here: https://cloud.google.com/nat/docs/ports-and-addresses#port-reservation-examples
In the example below 6 nodes are supported by the CloudNAT configuration and up to 20 nodes are allowed. The 7th node joining the cluster would fail due to the lack of free ports on the manual nat IP address which could be assigned. 4 Nat IPs would be needed to cover the 20 nodes.
Such upscaling failures could be covered by a proper validation.
The text was updated successfully, but these errors were encountered: