Skip to content

MON-4496: metrics: migrate Prometheus SD from Endpoints to EndpointSlices#668

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
jan--f:endpoints-to-endpointslices
Mar 13, 2026
Merged

MON-4496: metrics: migrate Prometheus SD from Endpoints to EndpointSlices#668
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
jan--f:endpoints-to-endpointslices

Conversation

@jan--f
Copy link
Contributor

@jan--f jan--f commented Feb 18, 2026

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 18, 2026
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Feb 18, 2026

@jan--f: This pull request references MON-4496 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

See also openshift/csi-operator#504

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested review from dfajmon and mpatlasov February 18, 2026 10:51
Signed-off-by: Jan Fajerski <jfajersk@redhat.com>
@dfajmon
Copy link
Contributor

dfajmon commented Mar 9, 2026

/retest

@dfajmon
Copy link
Contributor

dfajmon commented Mar 10, 2026

/approve
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 10, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 10, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dfajmon, jan--f

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-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 10, 2026
@dfajmon
Copy link
Contributor

dfajmon commented Mar 10, 2026

/verified by CI

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Mar 10, 2026
@openshift-ci-robot
Copy link
Contributor

@dfajmon: This PR has been marked as verified by CI.

Details

In response to this:

/verified by CI

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 openshift-eng/jira-lifecycle-plugin repository.

@jan--f
Copy link
Contributor Author

jan--f commented Mar 12, 2026

/retest

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 13, 2026

@jan--f: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/hypershift-e2e-aks 4031bf5 link true /test hypershift-e2e-aks

Full PR test history. Your PR dashboard.

Details

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. I understand the commands that are listed here.

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD ba77c76 and 2 for PR HEAD 4031bf5 in total

@openshift-merge-bot openshift-merge-bot bot merged commit c060317 into openshift:main Mar 13, 2026
16 of 17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants