Avoid kuma.io/service matching in the api

kumahq / kuma

🐻 The multi-zone service mesh for containers, Kubernetes and VMs. Built with Envoy. CNCF Sandbox Project.

https://kuma.io/install

Apache License 2.0

3.55k stars 327 forks source link

Avoid kuma.io/service matching in the api #9301

Open lahabana opened 4 months ago

lahabana commented 4 months ago

What happened?

In policy matching kuma.io/service should just be a label like any other.

this implies we should:

use MeshGateway for gateway and MeshService for services. MeshSubset is only usable in from or top level
Introduce MeshExternalService to match an external service

What does this mean that Mesh or MeshSubset ? Do they select externalServices? Do we need another proxy type for them?

why do this?

it solves multiple issues and confusions: TODO add them

jakubdyszkiewicz commented 4 months ago

xref:

github-actions[bot] commented 1 month ago

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.

lahabana commented 1 month ago

Triage: Needs MeshService to be complete to be able to progress on this