-
Notifications
You must be signed in to change notification settings - Fork 281
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
Add displayName as a possible tag for k8s candidate matching #1856
Conversation
@@ -4,8 +4,10 @@ lookups: | |||
- domain: INFRA | |||
type: KUBERNETESCLUSTER | |||
tags: | |||
matchingMode: ANY | |||
matchingMode: FIRST |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We are changing the matching mode and it is not present on the description of the PR.
Could we please include the reasoning for this change on the PR description?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we please include the reasoning for the matching mode change on the PR description?
…c#1856) Co-authored-by: nephyst <[email protected]> Co-authored-by: Otávio Carvalho <[email protected]>
Relevant information
Adding displayName as a possible tag for matching k8s candidate relationships. We expect displayName to match in the majority of cases, which is why it is being checked before k8s.cluster.name.
The matching mode is being changed to FIRST as we are using this to determine which cluster is being managed by a specific agent, and only want a single target entity to have a relationship synthesized.
Checklist
identifier
will be unique and valid.