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

Allow specifying specific pod events to fail workspaces when encountered #1279

Open
AObuchow opened this issue Jun 26, 2024 · 0 comments
Open
Assignees
Labels
enhancement New feature or request

Comments

@AObuchow
Copy link
Collaborator

Description

Currently, we have a hard-coded list of pod events that will result in a workspace failing if they are encountered. However, there is no way to add additional events that should result in a workspace failing.

We could potentially add a new DWOC field UnrecoverableEvents that includes a list of pod events that should result workspace failure. It'd be nice to also include the threshold of how many times this event should occur before workspace failure, but we've had issues with event count in the past on OpenShift, and I'm not sure if that's still the case.

Additional context

We want to remove the FailedScheduling event from being in the default, hard-coded list of events that cause workspace failures if encountered. However, users need to be able to add this event back to the list of unrecoverable events.

@AObuchow AObuchow added the enhancement New feature or request label Jun 26, 2024
@AObuchow AObuchow moved this to 📋 Backlog (not in current Sprint) in Eclipse Che Team B Backlog Jul 9, 2024
@dkwon17 dkwon17 moved this from 📋 Backlog (not in current Sprint) to 📅 Planned for this Sprint in Eclipse Che Team B Backlog Jul 17, 2024
@dkwon17 dkwon17 moved this from 📅 Planned for this Sprint to 📋 Backlog (not in current Sprint) in Eclipse Che Team B Backlog Sep 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant