Proposed change
I demo'd #910 recently to a user community and received some interesting feedback: they'd like the option to mute certain messages displayed to the end-user as they unnecessarily create fear that something's gone wrong when it hasn't. A good example is when there a node scale up is required and the user is met with a warning message that says
"0/4 nodes are available: 1 Insufficient cpu, 1 Insufficient memory, 3 node(s) didn't match Pod's node affinity/selector. preemption: 0/4 nodes are available: 1 No preemption victims found for incoming pod, 3 Preemption is not helpful for scheduling.",
when actually, for the end-user, nothing has actually gone wrong yet.
Alternative options
The alternative option would be to do nothing and not improve the user-friendliness of the spawn progress page.
Who would use this feature?
The main beneficiary is the end-user who might not have prior knowledge and experience of kubernetes, and therefore would appreciate progress messages that does not comprise of raw k8 events messages.
(Optional): Suggest a solution
Given the ruleformatter introduced by #910, it would be nice to extend that with a config option to not pipe certain messages to the end-user.
Proposed change
I demo'd #910 recently to a user community and received some interesting feedback: they'd like the option to mute certain messages displayed to the end-user as they unnecessarily create fear that something's gone wrong when it hasn't. A good example is when there a node scale up is required and the user is met with a warning message that says
when actually, for the end-user, nothing has actually gone wrong yet.
Alternative options
The alternative option would be to do nothing and not improve the user-friendliness of the spawn progress page.
Who would use this feature?
The main beneficiary is the end-user who might not have prior knowledge and experience of kubernetes, and therefore would appreciate progress messages that does not comprise of raw k8 events messages.
(Optional): Suggest a solution
Given the ruleformatter introduced by #910, it would be nice to extend that with a config option to not pipe certain messages to the end-user.