forked from open-telemetry/opentelemetry-collector-contrib
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathk8scluster-entities-relationships.yaml
More file actions
22 lines (17 loc) · 1.06 KB
/
k8scluster-entities-relationships.yaml
File metadata and controls
22 lines (17 loc) · 1.06 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
# Use this changelog template to create an entry for release notes.
# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
change_type: enhancement
# The name of the component, or a single word describing the area of concern, (e.g. receiver/filelog)
component: receiver/k8s_cluster
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
note: Define entities and relationships for Kubernetes resources in metadata.yaml.
# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
issues: [41080]
# If your change doesn't affect end users or the exported elements of any package,
# you should instead start your pull request title with [chore] or use the "Skip Changelog" label.
# Optional: The change log or logs in which this entry should be included.
# e.g. '[user]' or '[user, api]'
# Include 'user' if the change is relevant to end users.
# Include 'api' if there is a change to a library API.
# Default: '[user]'
change_logs: [user]