-
Notifications
You must be signed in to change notification settings - Fork 173
Expand file tree
/
Copy pathopenshift-resource-detection.yaml
More file actions
21 lines (21 loc) · 1.49 KB
/
openshift-resource-detection.yaml
File metadata and controls
21 lines (21 loc) · 1.49 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
# 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. agent, clusterReceiver, gateway, operator, chart, other)
component: agent, clusterReceiver, gateway
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
note: Add OpenShift resource detection support
# One or more tracking issues related to the change
issues: [2330]
# (Optional) One or more lines of additional information to render under the primary note.
# These lines will be padded with 2 spaces and then inserted directly into the document.
# Use pipe (|) for multiline entries.
subtext: |
When distribution is set to "openshift", the openshift detector is enabled regardless of
cloudProvider. It auto-discovers k8s.cluster.name, cloud.provider, cloud.platform, and
cloud.region via the OpenShift API (config.openshift.io/v1/infrastructures). The
cloud.platform value reflects the actual hosting environment (e.g., aws_openshift,
gcp_openshift, azure.openshift). Cloud-provider-specific detectors are also enabled
alongside the openshift detector to collect instance metadata: ec2 on AWS, gcp on GCP,
and azure on Azure. Distribution-specific detectors (openshift, aks) now take priority
over the cloud-provider catch-all in detector selection, ensuring the correct
cloud.platform is always set. The clusterName field is now optional for OpenShift.