Skip to content

[18-stable] Remove unhelpful labelDrops in scrapeConfig - #1112

Merged
openshift-merge-bot[bot] merged 1 commit into
openstack-k8s-operators:18-stablefrom
openshift-cherrypick-robot:cherry-pick-1011-to-18-stable
Oct 23, 2026
Merged

openshift-merge-bot[bot] merged 1 commit into
openstack-k8s-operators:18-stablefrom
openshift-cherrypick-robot:cherry-pick-1011-to-18-stable

Conversation

@openshift-cherrypick-robot

Copy link
Copy Markdown

This is an automated cherry-pick of #1011

/assign vyzigold

This was reported informally as a bug agaisnt this example alert: https://github.com/openstack-k8s-operators/telemetry-operator/blob/main/docs/sample-alerts/openstack-observability-services-status.yaml#L23

User states that Pod label doesn't exist.

This labelDrop configuration dates back to STF, when none of the OSP17 services ran in OCP. These labels were meaningless/misleading at the time, always reflecting values of the smart-gateway rather than the actual services in question (nothing in the OSP17 control-plane ran in a "pod" or "namespace", and the "job" was always the same).

I've opted to continue to drop "publisher", concurring with Juan's opinion on the matter. I've checked it and says "ceilometer" on 171 series in my environment, and "ceilometer-0" on 1 series. That's a question I'm not going to tackle right now, but the label doesn't seem terribly useful, so we'll continue to drop it.
@coderabbitai

coderabbitai Bot commented Oct 23, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Central YAML (base), Organization UI (inherited)
  • Review profile: CHILL
  • Plan: Enterprise
  • Run ID: 28ef0a4b-3383-4818-bcd0-917bbefc6ae0

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Comment @coderabbitai help to get the list of available commands.

@vyzigold

Copy link
Copy Markdown
Contributor

/cherry-pick 18.0-fr7

@openshift-cherrypick-robot

Copy link
Copy Markdown
Author

@vyzigold: once the present PR merges, I will cherry-pick it on top of 18.0-fr7 in a new PR and assign it to you.

Details

In response to this:

/cherry-pick 18.0-fr7

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-ci openshift-ci Bot added the lgtm label Oct 23, 2026
@openshift-ci

openshift-ci Bot commented Oct 23, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: openshift-cherrypick-robot, vyzigold

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-bot
openshift-merge-bot Bot merged commit 6910c32 into openstack-k8s-operators:18-stable Oct 23, 2026
5 checks passed
@openshift-cherrypick-robot

Copy link
Copy Markdown
Author

@vyzigold: new pull request created: #1113

Details

In response to this:

/cherry-pick 18.0-fr7

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants