|
| 1 | +# Use this changelog template to create an entry for release notes. |
| 2 | +# |
| 3 | +# If your change doesn't affect end users you should instead start |
| 4 | +# your pull request title with [chore] or use the "Skip Changelog" label. |
| 5 | + |
| 6 | +# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix' |
| 7 | +change_type: breaking |
| 8 | + |
| 9 | +# The name of the area of concern in the attributes-registry, (e.g. http, cloud, db) |
| 10 | +component: k8s |
| 11 | + |
| 12 | +# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). |
| 13 | +note: "Fix plural-named updowncounter k8s metrics; replace with singular + .count names." |
| 14 | + |
| 15 | +# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists. |
| 16 | +# The values here must be integers. |
| 17 | +issues: [2301] |
| 18 | + |
| 19 | +# (Optional) One or more lines of additional information to render under the primary note. |
| 20 | +# These lines will be padded with 2 spaces and then inserted directly into the document. |
| 21 | +# Use pipe (|) for multiline entries. |
| 22 | +subtext: | |
| 23 | + Renamed metrics: |
| 24 | + - k8s.daemonset.current_scheduled_nodes -> k8s.daemonset.current_scheduled_node.count |
| 25 | + - k8s.daemonset.desired_scheduled_nodes -> k8s.daemonset.desired_scheduled_node.count |
| 26 | + - k8s.daemonset.misscheduled_nodes -> k8s.daemonset.misscheduled_node.count |
| 27 | + - k8s.daemonset.ready_nodes -> k8s.daemonset.ready_node.count |
| 28 | + - k8s.job.active_pods -> k8s.job.active_pod.count |
| 29 | + - k8s.job.failed_pods -> k8s.job.failed_pod.count |
| 30 | + - k8s.job.successful_pods -> k8s.job.successful_pod.count |
| 31 | + - k8s.job.desired_successful_pods -> k8s.job.desired_successful_pod.count |
| 32 | + - k8s.job.max_parallel_pods -> k8s.job.max_parallel_pod.count |
| 33 | + - k8s.cronjob.active_jobs -> k8s.cronjob.active_job.count |
0 commit comments