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

[GEP-1651] add a note about multi-network + routability #2441

Merged
merged 1 commit into from
Feb 29, 2024
Merged

[GEP-1651] add a note about multi-network + routability #2441

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions geps/gep-1651/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -251,6 +251,15 @@ We plan on introducing a new type `GatewayStatusAddress` and change Gateway's `s
It is RECOMMENDED that in-cluster gateways SHOULD NOT support 'Private' routability. Kubernetes doesn't have
a concept of 'Private' routability for Services. In the future this may change upstream.

#### Interaction with Multi-Network Kubernetes

[Multi-Network Kubernetes](https://github.com/kubernetes/enhancements/pull/3700)
is a sibling SIG working on adding multi-network support to Pods. After reaching out and having a discussion with about this GEP
the consensus is that a Gateway most likely in the future can be tied to a single PodNetwork. Defining this is out of scope for this GEP.

A second consensus is the Routabilities defined in this GEP don't impact PodNetworks but instead are indicators to LB implementations
on how they should behave.

## Examples

#### 1. Request a GatewayAddress that is routable within the same cluster
Expand Down