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

[ptrivedi]

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]

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

[k8s-triage-robot]

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

[robscott]

/remove-lifecycle stale

[k8s-triage-robot]

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