Skip to content

Show inbound and outbound listing based on new _layout endpoint (without passthrough) #4119

Description

@slonka

Description

This is the view we're talking about:

Image

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:

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

Use proxyResourceName on the lists.

KRI is in the form of:

fmt.Sprintf("kri_%s_%s_%s_%s_%s_%s", desc.ShortName, i.Mesh, i.Zone, i.Namespace, i.Name, i.SectionName)

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

  • Show the inbounds and outbounds with new names
  • Do not show "Total connections", "Bytes received", "Bytes sent" - this will be a separate PR after stats handling is done

Metadata

Metadata

Assignees

Labels

kind/featureNew featuretriage/acceptedThe issue was reviewed and is complete enough to start working on it

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions