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

make failed scale ups a warning #298

Open
epDHowwD opened this issue Mar 7, 2024 · 0 comments
Open

make failed scale ups a warning #298

epDHowwD opened this issue Mar 7, 2024 · 0 comments
Labels
kind/enhancement Enhancement, improvement, extension lifecycle/stale Nobody worked on this for 6 months (will further age)

Comments

@epDHowwD
Copy link

epDHowwD commented Mar 7, 2024

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"

image

@epDHowwD epDHowwD added the kind/enhancement Enhancement, improvement, extension label Mar 7, 2024
@gardener-robot gardener-robot added the lifecycle/stale Nobody worked on this for 6 months (will further age) label Nov 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement Enhancement, improvement, extension lifecycle/stale Nobody worked on this for 6 months (will further age)
Projects
None yet
Development

No branches or pull requests

2 participants