There are many cases where causing the FailedScheduling event to result in workspace failure is problematic. For example, flaky cluster infrastructure can require multiple attempts to schedule a workspace pod on a cluster. Additionally, the cluster auto-scaler can only kick in when a pod remains in the unschedulable state -- if we delete the deployment immediately after a pod is deteremiend to be unschedulable, the auto-scaler cannot kick in.
Thus we should remove the FailedScheduling event from the list of unrecoverable workspace pod events. https://github.com/devfile/devworkspace-operator/issues/1279 is required to allow users the ability to re-add the FailedScheduling event to the list of unrecoverable workspace pod events.
There are many cases where causing the FailedScheduling event to result in workspace failure is problematic. For example, flaky cluster infrastructure can require multiple attempts to schedule a workspace pod on a cluster. Additionally, the cluster auto-scaler can only kick in when a pod remains in the unschedulable state -- if we delete the deployment immediately after a pod is deteremiend to be unschedulable, the auto-scaler cannot kick in.
Thus we should remove the FailedScheduling event from the list of unrecoverable workspace pod events. https://github.com/devfile/devworkspace-operator/issues/1279 is required to allow users the ability to re-add the FailedScheduling event to the list of unrecoverable workspace pod events.