Skip to content

google grpc: allow custom prefix paths for grpc #45964

Description

@AntonKanug

Use-case:
When there is a L7 proxy in between multiple control planes, the proxy cannot distinguish which control plane the xds grpc is for by path.

cluster.com/my-control-plane-1/envoy.service.discovery.v3.AggregatedDiscoveryService
cluster.com/my-control-plane-2/envoy.service.discovery.v3.AggregatedDiscoveryService

I have done this in our fork and is using it internally but is looking to contribute this as a feature.

Can also follow up with go/java control plane support for this out of the box when configuring the xds server.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementFeature requests. Not bugs or questions.triageIssue requires triage

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions