Support `connectionPool` and `loadBalancer` from Gateway to Backend

kubernetes-sigs / gateway-api

Repository for the next iteration of composite service (e.g. Ingress) and load balancing APIs.

https://gateway-api.sigs.k8s.io

Apache License 2.0

1.81k stars 469 forks source link

Support `connectionPool` and `loadBalancer` from Gateway to Backend #2005

Open machine3 opened 1 year ago

machine3 commented 1 year ago

What would you like to be added: Support connectionPool and loadBalancer from Gateway to Backend. Just like Istio DestinationRule

apiVersion: networking.istio.io/v1alpha3
kind: DestinationRule
metadata:
  name: my-destination-rule
spec:
  host: my-svc
  trafficPolicy: 
    connectionPool: <-- here
    loadBalancer:  <-- here
  subsets:
  - name: v1
    labels:
      version: v1
  - name: v2
    labels:
      version: v2
    trafficPolicy: 
      connectionPool: <-- here
      loadBalancer:  <-- here
  - name: v3
    labels:
      version: v3

Why this is needed:

arkodg commented 1 year ago

I vote to change the title & description to support connectionPool and loadBalancer from Gateway to Backend

shaneutt commented 1 year ago

This is an interesting idea which would need to be proposed as a GEP.

/triage accepted /kind gep

However we're currently focused on getting our GA release completed (see milestone v1.0.0) and this would not seem to be something that would need to block the release, so we're not ready to prioritize this and we would ask that v1.0.0 milestone issues get priority so we can focus there, and come back to this after the release.

k8s-triage-robot commented 3 months ago

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

Confirm that this issue is still relevant with /triage accepted (org members only)
Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

k8s-triage-robot commented 3 weeks ago

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