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

Validate CloudNAT and Woker configuration in shoot spec. #417

Open
DockToFuture opened this issue Mar 28, 2022 · 1 comment
Open

Validate CloudNAT and Woker configuration in shoot spec. #417

DockToFuture opened this issue Mar 28, 2022 · 1 comment
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

Comments

@DockToFuture
Copy link
Member

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.

    infrastructureConfig:
      networks:
        cloudNAT:
          minPortsPerVM: 10000
          natIPNames:
            - name: manual-nat-01
        workers: 10.250.0.0/16
...
    workers:
      - cri:
          name: docker
        name: worker-group-1
        machine:
          type: n1-standard-2
          image:
            name: gardenlinux
            version: 576.3.0
        maximum: 20
        minimum: 1
...

Such upscaling failures could be covered by a proper validation.

@DockToFuture DockToFuture added the kind/enhancement Enhancement, improvement, extension label Mar 28, 2022
@gardener-robot gardener-robot added area/networking Networking related platform/gcp Google cloud platform/infrastructure labels Mar 28, 2022
@gardener-robot gardener-robot added the lifecycle/stale Nobody worked on this for 6 months (will further age) label Sep 25, 2022
@gardener-robot gardener-robot added lifecycle/rotten Nobody worked on this for 12 months (final aging stage) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Jun 5, 2023
@kon-angelo
Copy link
Contributor

/remove lifecycle/rotten

@gardener-robot gardener-robot removed the lifecycle/rotten Nobody worked on this for 12 months (final aging stage) label Aug 16, 2023
@gardener-robot gardener-robot added the lifecycle/stale Nobody worked on this for 6 months (will further age) label Apr 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Projects
None yet
Development

No branches or pull requests

3 participants