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

Allow specifying NAT Gateways, subnets and routes when creating cluster. #189

Open
mvladev opened this issue Sep 28, 2020 · 0 comments
Open
Labels
area/cost Cost related kind/enhancement Enhancement, improvement, extension lifecycle/rotten Nobody worked on this for 12 months (final aging stage) platform/aws Amazon web services platform/infrastructure priority/3 Priority (lower number equals higher priority)

Comments

@mvladev
Copy link

mvladev commented Sep 28, 2020

How to categorize this issue?

/area cost
/kind enchancement
/priority normal
/platform aws

What would you like to be added:

Allow for usage of pre-created AWS infrastructure as it would reduce costs (e.g. sharing NAT Gateways between clusters) and speed up the creation of the cluster. This would also further allow for full control over the network routing and design.

All resources must be tagged with "kubernetes.io/cluster/{{cluster-id}}" = "1" where cluster-id is shoot--{{project-name}}--{{shoot-name}} and the subnet used for internal LB should also be tagged with "kubernetes.io/role/internal-elb" = "use".

Why is this needed:

  • Reduced costs
  • Faster cluster creation
  • Network customization
@mvladev mvladev added the kind/enhancement Enhancement, improvement, extension label Sep 28, 2020
@gardener-robot gardener-robot added area/cost Cost related platform/aws Amazon web services platform/infrastructure priority/normal labels Sep 28, 2020
@gardener gardener deleted a comment from gardener-robot Sep 28, 2020
@gardener gardener deleted a comment from gardener-robot Sep 28, 2020
@gardener-robot gardener-robot added the lifecycle/stale Nobody worked on this for 6 months (will further age) label Nov 28, 2020
@gardener-robot gardener-robot added priority/3 Priority (lower number equals higher priority) and removed priority/normal labels Mar 8, 2021
@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 Sep 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/cost Cost related kind/enhancement Enhancement, improvement, extension lifecycle/rotten Nobody worked on this for 12 months (final aging stage) platform/aws Amazon web services platform/infrastructure priority/3 Priority (lower number equals higher priority)
Projects
None yet
Development

No branches or pull requests

2 participants