You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think the most suitable way to implement this is to provide implementation to this
type ResourceGenerator interface {
Generate(xds_context.Context, *model.Proxy) ([]*model.Resource, error)
}
This will be a merge of InboundProxyGenerator and OutboundProxyGenerator.
Given such Ingress dataplane
type: Dataplane
mesh: default
name: ingress-1
networking:
ingress: true # to decide: we need a marker that this is an ingress
address: 1.1.1.4
inbound:
- port: 10000 # picked automatically
tags:
service: backend
cluster: cluster-1
- port: 10001 # picked automatically
tags:
service: backend
version: v2
cluster: cluster-1
We will open 2 inbound listeners, create 2 Envoy clusters. Each Envoy cluster will have corresponding EDS with endpoints for all DPs (inbounds) in a Kuma cluster.
The text was updated successfully, but these errors were encountered:
Summary
Generate XDS for Ingress Dataplane.
Implementation tips:
I think the most suitable way to implement this is to provide implementation to this
This will be a merge of
InboundProxyGenerator
andOutboundProxyGenerator
.Given such Ingress dataplane
We will open 2 inbound listeners, create 2 Envoy clusters. Each Envoy cluster will have corresponding EDS with endpoints for all DPs (inbounds) in a Kuma cluster.
The text was updated successfully, but these errors were encountered: