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

Define default resource requests for comonent gardener-extension-admission-shoot-dns #339

Open
andrerun opened this issue Jun 6, 2024 · 0 comments
Labels
area/control-plane Control plane related kind/enhancement Enhancement, improvement, extension

Comments

@andrerun
Copy link
Contributor

andrerun commented Jun 6, 2024

How to categorize this issue?
/area control-plane
/kind enhancement

What would you like to be added:
The gardener-extension-admission-shoot-dns-service component, running in the garden namespace in the garden runtime cluster, currently does not specify resource requests, and initially runs as a "best effort" pod until it is evicted and VPA sets a value for requests. In theory, we could improve initial pod placement and increase the mean time to first eviction by providing appropriate default requests.

Why is this needed:
That would be a minor improvement and this issue is filed for general tracking purposes, not because of any urgent problem. The suggested improvement should result in a minor reduction in the frequency of eviction-driven webhook latency spikes.

@gardener-robot gardener-robot added area/control-plane Control plane related kind/enhancement Enhancement, improvement, extension labels Jun 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/control-plane Control plane related kind/enhancement Enhancement, improvement, extension
Projects
None yet
Development

No branches or pull requests

2 participants