Open geowalrus4gh opened 3 months ago
Just a clarification from some outside context - this is for Mesh usage not Gateway I believe
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
What would you like to be added:
A source label match feature to match the request based on the source pod identification at the target service being called. This identification can be based on labels given in the source pod specification
Why this is needed: We have a use case to identify the source pod based on the label. We have to write some rules in the target service based on this matching.
currently we use specific implementation from Istio's sourceLabel feature in the HTTPMatchRequest