Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing docs about MeshSubset and MeshServiceSubset #2086

Open
schogges opened this issue Nov 13, 2024 · 2 comments
Open

Missing docs about MeshSubset and MeshServiceSubset #2086

schogges opened this issue Nov 13, 2024 · 2 comments
Labels
kind/feature New feature triage/accepted The issue was reviewed and is complete enough to start working on it

Comments

@schogges
Copy link
Contributor

Description

In the docs there are many occurrences of MeshSubset and MeshServiceSubset, but I could not find a dedicate documentation about these resources. In the code I could find something in the app/_posts/2022-12-20-policy.md.

MeshSubset: a subset of dataplane proxies across all services that have a set of tags

targetRef:
 kind: MeshSubset
 tags:
   k8s.kuma.io/namespace: ns-1

MeshServiceSubset: Like MeshService with extra tags to select a subset of all dataplanes. For example you could pick only dataplanes with the tag version: v2.

targetRef:
 kind: MeshServiceSubset
 name: backend_ns1_svc_80
 tags:
   version: v2
@schogges schogges added kind/feature New feature triage/pending This issue will be looked at on the next triage meeting labels Nov 13, 2024
@michaelbeaumont
Copy link
Contributor

We talk about them in the policy introduction but part of the problem is probably that this is impossible to find by searching

@lobkovilya
Copy link
Contributor

Triage: we should make sure targetRef kinds explained here https://kuma.io/docs/2.9.x/policies/introduction/#writing-a-targetref pop up in the search.

@lobkovilya lobkovilya added triage/accepted The issue was reviewed and is complete enough to start working on it and removed triage/pending This issue will be looked at on the next triage meeting labels Nov 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature New feature triage/accepted The issue was reviewed and is complete enough to start working on it
Projects
None yet
Development

No branches or pull requests

3 participants