You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We see that our developers during debugging and our operations get drowned in info events on pods that node groups are not suitable for the pod due to nodeSelectors, affinities or taints. Within these hundreds of events, there are messages hidden that some groups, which would fit, failed to scale up. Failed scale ups are an issue and often the cause for pods not being scheduable. Please make this a warning to highlight the importance for the reader. Then the event would be shown at the top of the events list. If you also change the formatting of the message to look a bit different than the other events this might be further improve.
Current: "INFO: pod didn't trigger scale-up: backoff after failed scale-up"
Better: "WARNING: scale-up group xyz triggered by pod failed with retrying with backoff"
The text was updated successfully, but these errors were encountered:
We see that our developers during debugging and our operations get drowned in info events on pods that node groups are not suitable for the pod due to nodeSelectors, affinities or taints. Within these hundreds of events, there are messages hidden that some groups, which would fit, failed to scale up. Failed scale ups are an issue and often the cause for pods not being scheduable. Please make this a warning to highlight the importance for the reader. Then the event would be shown at the top of the events list. If you also change the formatting of the message to look a bit different than the other events this might be further improve.
The text was updated successfully, but these errors were encountered: