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.

Sign up for GitHub

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

Jump to bottom

Disable deployment of allow-{TCP/UDP}-egress services when NAT Gateway is used #293

Open
kon-angelo opened this issue May 7, 2021 · 2 comments
Open

Disable deployment of allow-{TCP/UDP}-egress services when NAT Gateway is used #293

kon-angelo opened this issue May 7, 2021 · 2 comments
Assignees
@kon-angelo
Labels
area/control-plane Control plane related kind/enhancement Enhancement, improvement, extension lifecycle/stale Nobody worked on this for 6 months (will further age) platform/azure Microsoft Azure platform/infrastructure priority/3 Priority (lower number equals higher priority)

Comments

@kon-angelo
Copy link
Contributor

How to categorize this issue?

/area control-plane
/kind enhancement
/priority 3
/platform azure

What would you like to be added:
Disable the deployment of the `allow-{tcp,udp}-egress services used to configure egress traffic on Azure's Standard LBs when the shoot is using NAT Gateway.

Why is this needed:
The services are unnecessary if the NatGateway is used. Furthermore this change allows for cost optimisation since there are less resources needed for a minimal shoot.
@kon-angelo kon-angelo added the kind/enhancement Enhancement, improvement, extension label May 7, 2021
@gardener-robot gardener-robot added area/control-plane Control plane related platform/azure Microsoft Azure platform/infrastructure priority/3 Priority (lower number equals higher priority) labels May 7, 2021
@kon-angelo kon-angelo self-assigned this May 7, 2021
@gardener-robot gardener-robot added the lifecycle/stale Nobody worked on this for 6 months (will further age) label Nov 4, 2021
@dkistner dkistner mentioned this issue Nov 8, 2021
Closed
@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 May 5, 2022
@elchead elchead mentioned this issue Oct 20, 2022
Closed
@kon-angelo
Copy link
Contributor Author

/remove lifecycle/rotten

@gardener-robot gardener-robot removed the lifecycle/rotten Nobody worked on this for 12 months (final aging stage) label Dec 2, 2022
@ebensom
Copy link

ebensom commented Jul 10, 2023

Hi @kon-angelo,

Our projects use around 200 legacy Azure clusters where the NAT gateway is not enabled. One Public IP costs 0.005 cent / hour, which is 3.6 dollars per 30 days, and there are 2 public IPs created per cluster (allow-tcp-egress and allow-udp-egress). 200 * 7.2 dollars * 12 month is 17280 dollars per year, which is a good room for cost optimization.

Could this enhancement be prioritized?

@gardener-robot gardener-robot added the lifecycle/stale Nobody worked on this for 6 months (will further age) label Mar 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kon-angelo kon-angelo

Labels
area/control-plane Control plane related kind/enhancement Enhancement, improvement, extension lifecycle/stale Nobody worked on this for 6 months (will further age) platform/azure Microsoft Azure platform/infrastructure priority/3 Priority (lower number equals higher priority)
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

No egress when NAT-Gateway is used elchead/gardener-extension-provider-azure
3 participants
@ebensom @gardener-robot @kon-angelo