Remove cronjob-monitor #5851
Merged
Remove cronjob-monitor #5851
Conversation
This file contains 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
|
..removed to wait for e2e |
Signed-off-by: Mikkel Oscar Lyderik Larsen <[email protected]>
mikkeloscar
force-pushed
the
drop-cronjob-monitor
branch
from
5936fc9 to
fd2a075
Compare
|
👍 |
1 similar comment
|
👍 |
Merged
Merged
AlexanderYastrebov
added a commit
that referenced
this pull request
Mar 5, 2024
Follow up on #5851 and #7120 Signed-off-by: Alexander Yastrebov <[email protected]>
AlexanderYastrebov
added a commit
that referenced
this pull request
Mar 5, 2024
Follow up on #5851, #5857 and #7120 Signed-off-by: Alexander Yastrebov <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This removes the
cronjob-monitorcomponent which is no longer needed since Kubernetes v1.22.This component was setting the annotation
experimental.zalando.org/last-successful-completion-timeon successful cronjobs which was used in ZMON monitoring. Since Kubernetes v1.22 the same data is natively available in thestatus.lastSuccessfulTimefield and ZMON is already relying on that.