Skip to content

GEP: Gateway API to Expose Pods on Cluster-Internal IP Address (ClusterIP) #3539

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
Open
ptrivedi opened this issue Jan 7, 2025 · 3 comments · May be fixed by #3608
Open

GEP: Gateway API to Expose Pods on Cluster-Internal IP Address (ClusterIP) #3539

ptrivedi opened this issue Jan 7, 2025 · 3 comments · May be fixed by #3608
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@ptrivedi
Copy link

ptrivedi commented Jan 7, 2025

What would you like to be added:
We need to define via documentation how Gateway API can be used to accomplish ClusterIP Service behavior. As part of this definition, we want to

  1. Propose DNS record format for ClusterIP Gateway
  2. Propose an EndpointSelector resource to support Kubernetes resources besides Service (or external endpoints) directly as backendRefs
  3. Briefly touch on Gateway API usage to define other types of Services like LoadBalancer and NodePort

Why this is needed:
Service API has become inflexible and bloated over time, and has posed some practical challenges. There have been discussions around Gateway API replacing or substituting for Service API. We ran into challenges when trying to support ClusterIP Services for multi-network pods, which were cleanly solved by Gateway API.
@ptrivedi ptrivedi added the kind/feature Categorizes issue or PR as related to a new feature. label Jan 7, 2025
@ptrivedi
Copy link
Author

Shared this doc at the Jan 14 community meeting last week: https://docs.google.com/document/d/1N-C-dBHfyfwkKufknwKTDLAw4AP2BnJlnmx0dB-cC4U/edit?usp=sharing
Supporting slides: https://docs.google.com/presentation/d/1XjdLldZz7M3QRdMXuB_iIyOV88PNprjxduPJV8hN7T0/edit?usp=sharing

Planning a follow-up GEP after gathering some feedback on the doc

@robscott robscott mentioned this issue Jan 24, 2025
Merged
@ptrivedi ptrivedi mentioned this issue Feb 7, 2025
Closed
@mskrocki mskrocki mentioned this issue Feb 7, 2025
Open
@ptrivedi ptrivedi linked a pull request Feb 10, 2025 that will close this issue
Open
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 21, 2025
@robscott
Copy link
Member

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 21, 2025
@tssurya tssurya mentioned this issue Apr 27, 2025
Open
@LionelJouin LionelJouin mentioned this issue May 18, 2025
Open
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Milestone
No milestone
4 participants
@robscott @ptrivedi @k8s-ci-robot @k8s-triage-robot