ScrapeConfig Status Subresource Removal from prometheus#7969
Merged
simonpasquier merged 6 commits intoprometheus-operator:mainfrom Oct 3, 2025
Merged
ScrapeConfig Status Subresource Removal from prometheus#7969simonpasquier merged 6 commits intoprometheus-operator:mainfrom
simonpasquier merged 6 commits intoprometheus-operator:mainfrom
Conversation
Contributor
Author
|
@simonpasquier PTAL |
Contributor
|
CI isn't happy :) |
Contributor
Author
|
ping @simonpasquier |
simonpasquier
approved these changes
Oct 3, 2025
3b33e68
into
prometheus-operator:main
21 of 22 checks passed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
ScrapeConfig Status Subresource Removal from prometheus
Closes: #7961
Type of change
What type of changes does your code introduce to the Prometheus operator? Put an
xin the box that apply.CHANGE(fix or feature that would cause existing functionality to not work as expected)FEATURE(non-breaking change which adds functionality)BUGFIX(non-breaking change which fixes an issue)ENHANCEMENT(non-breaking change which improves existing functionality)NONE(if none of the other choices apply. Example, tooling, build system, CI, docs, etc.)Verification
Please check the Prometheus-Operator testing guidelines for recommendations about automated tests.
Changelog entry
Please put a one-line changelog entry below. This will be copied to the changelog file during the release process.