-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Provide condition for Manifests stuck in Deleting due to DefaultCR Warning #1988
Merged
lindnerby
merged 39 commits into
kyma-project:main
from
ruanxin:Provide-condition-and-metrics-for-Manifests-stuck-in-Deleting-state-due-to-DefaultCR-Warning
Nov 5, 2024
Merged
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
- extract code related to manifest.status to new package
…nd-metrics-for-Manifests-stuck-in-Deleting-state-due-to-DefaultCR-Warning
add RemoveModuleCR test
…nd-metrics-for-Manifests-stuck-in-Deleting-state-due-to-DefaultCR-Warning
kyma-bot
added
cla: yes
Indicates the PR's author has signed the CLA.
size/L
Denotes a PR that changes 100-499 lines, ignoring generated files.
labels
Oct 25, 2024
…uanxin/Provide-condition-and-metrics-for-Manifests-stuck-in-Deleting-state-due-to-DefaultCR-Warning
kyma-bot
added
size/XL
Denotes a PR that changes 500-999 lines, ignoring generated files.
and removed
size/L
Denotes a PR that changes 100-499 lines, ignoring generated files.
labels
Oct 31, 2024
…uanxin/Provide-condition-and-metrics-for-Manifests-stuck-in-Deleting-state-due-to-DefaultCR-Warning
ruanxin
changed the title
chore: Provide condition and metrics for Manifests stuck in Deleting due to DefaultCR Warning
chore: Provide condition for Manifests stuck in Deleting due to DefaultCR Warning
Nov 4, 2024
ruanxin
changed the title
chore: Provide condition for Manifests stuck in Deleting due to DefaultCR Warning
feat: Provide condition for Manifests stuck in Deleting due to DefaultCR Warning
Nov 4, 2024
…stuck-in-Deleting-state-due-to-DefaultCR-Warning
…stuck-in-Deleting-state-due-to-DefaultCR-Warning
lindnerby
requested changes
Nov 4, 2024
…r-Manifests-stuck-in-Deleting-state-due-to-DefaultCR-Warning' into fork/ruanxin/Provide-condition-and-metrics-for-Manifests-stuck-in-Deleting-state-due-to-DefaultCR-Warning
…e-condition-and-metrics-for-Manifests-stuck-in-Deleting-state-due-to-DefaultCR-Warning
…stuck-in-Deleting-state-due-to-DefaultCR-Warning
lindnerby
approved these changes
Nov 5, 2024
…stuck-in-Deleting-state-due-to-DefaultCR-Warning
New changes are detected. LGTM label has been removed. |
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.
Description
This PR
Related issue(s)
#1830