The view is similar but without passthrough and stats.
inbounds:
- kri: <resource_identifier> # Inbound KRI
port: <port_number> # port number
protocol: http # port protocol
proxyResourceName: <common_prefix>_<sectionName>
outbounds:
- kri: <resource_identifier> # MS/MMZS/MES resource identifier
port: <port_number> # MS/MMZS/MES exposed port number
protocol: TCP
proxyResourceName: <outbound_kri> # MS/MMZS/MES resource identifier
fmt.Sprintf("kri_%s_%s_%s_%s_%s_%s", desc.ShortName, i.Mesh, i.Zone, i.Namespace, i.Name, i.SectionName)
Description
This is the view we're talking about:
The view is similar but without passthrough and stats.
Based on https://github.com/kumahq/kuma/blob/master/docs/madr/decisions/078-include-envoy-resource-name-tp-in-layout-endpoint.md#decision it will take the form of:
Use
proxyResourceNameon the lists.KRI is in the form of:
Example of the names:
https://github.com/kumahq/kuma/blob/master/docs/madr/decisions/077-migrating-to-consistent-and-well-defined-naming-for-non-system-envoy-resources-and-stats.md#examples
It's defined here https://github.com/kumahq/kuma/blob/29d62590fdf1b203ec729192b03144e98aca3570/docs/generated/openapi.yaml#L3862 in the oapi spec.
Acceptance criteria