-
Notifications
You must be signed in to change notification settings - Fork 1
Reduce number of Istio Ingress Gateways #10
Copy link
Copy link
Open
Labels
Q2/2026This topic is relevant for the hackathon in Q2/2026.This topic is relevant for the hackathon in Q2/2026.area/costCost relatedCost relatedarea/networkingNetworking relatedNetworking relatedkind/enhancementEnhancement, improvement, extensionEnhancement, improvement, extensionlifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.teamsize/smallA team of 1-2 people.A team of 1-2 people.
Description
Metadata
Metadata
Assignees
Labels
Q2/2026This topic is relevant for the hackathon in Q2/2026.This topic is relevant for the hackathon in Q2/2026.area/costCost relatedCost relatedarea/networkingNetworking relatedNetworking relatedkind/enhancementEnhancement, improvement, extensionEnhancement, improvement, extensionlifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.teamsize/smallA team of 1-2 people.A team of 1-2 people.
Type
Fields
Give feedbackNo fields configured for issues without a type.
How to categorize this topic?
/area cost
/area networking
/kind enhancement
/label teamsize/small
What is the topic about?:
In a standard multi-zonal seed cluster, there is one multi-zonal istio ingress gateway and one per availability zone. The multi-zonal istio ingress gateway could be replaced by usage of all single-zone istio ingress gateways. This could lead to higher resource usage, reduced costs and a less complicated setup.