Skip to content
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

Enhance Error and Warning Visibility for Cluster Backup Resources #13439

Open
ahmadhamzh opened this issue Jun 10, 2024 · 5 comments
Open

Enhance Error and Warning Visibility for Cluster Backup Resources #13439

ahmadhamzh opened this issue Jun 10, 2024 · 5 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale. sig/app-management Denotes a PR or issue as being assigned to SIG App Management. sig/cluster-management Denotes a PR or issue as being assigned to SIG Cluster Management.
Milestone

Comments

@ahmadhamzh
Copy link
Contributor

Issue Description :

Currently, if there is an error or warning in any of the cluster backup resources (backup, schedule, and restore), the message is not displayed. This lack of visibility makes it challenging to debug errors effectively. To improve the debugging process, we need to ensure that error and warning messages are clearly shown for all cluster backup resources.

REF: kubermatic/dashboard#6701

@csengerszabo
Copy link
Contributor

/label sig/app-management

@kubermatic-bot kubermatic-bot added the sig/app-management Denotes a PR or issue as being assigned to SIG App Management. label Jun 10, 2024
@csengerszabo
Copy link
Contributor

/label sig/cluster-management

@kubermatic-bot kubermatic-bot added the sig/cluster-management Denotes a PR or issue as being assigned to SIG Cluster Management. label Jun 10, 2024
@kubermatic-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.
After a furter 30 days, they will turn rotten.
Mark the issue as fresh with /remove-lifecycle stale.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@kubermatic-bot kubermatic-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 8, 2024
@csengerszabo
Copy link
Contributor

/milestone KKP 2.27

@kubermatic-bot kubermatic-bot added this to the KKP 2.27 milestone Oct 1, 2024
@kubermatic-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

@kubermatic-bot kubermatic-bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale. sig/app-management Denotes a PR or issue as being assigned to SIG App Management. sig/cluster-management Denotes a PR or issue as being assigned to SIG Cluster Management.
Projects
None yet
Development

No branches or pull requests

3 participants