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.

Sign up for GitHub

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

Jump to bottom

Support extended resources in provider config node template without re-specifying core resources #1009

Closed
elankath opened this issue Jul 18, 2024 · 1 comment · Fixed by #1010
Closed

Support extended resources in provider config node template without re-specifying core resources #1009

elankath opened this issue Jul 18, 2024 · 1 comment · Fixed by #1010
Assignees
@elankath
Labels
area/auto-scaling Auto-scaling (CA/HPA/VPA/HVPA, predominantly control plane, but also otherwise) related kind/enhancement Enhancement, improvement, extension platform/aws Amazon web services platform/infrastructure status/closed Issue is closed (either delivered or triaged)

Comments

@elankath
Copy link
Contributor

How to categorize this issue?

/area auto-scaling
/kind enhancement
/platform aws

What would you like to be added:

Permit specification of custom extended resources in the worker.providerConfig.nodeTemplate without needing to explicitly re-specify core resources such as cpu, gpu, memory for the machine type again.

Why is this needed:
This is needed for support of gardener/autoscaler#132. This will permit stakeholders to have custom extended resources associated with Nodes, thus permitting Pods specs with requests for these custom extended resources and leveraging the scheduling support by the kube-scheduler

(see HANA-27484 for extended details)
@gardener-robot gardener-robot added area/auto-scaling Auto-scaling (CA/HPA/VPA/HVPA, predominantly control plane, but also otherwise) related kind/enhancement Enhancement, improvement, extension platform/aws Amazon web services platform/infrastructure labels Jul 18, 2024
@elankath
Copy link
Contributor Author

/assign @elankath
/assign elankath

@elankath elankath mentioned this issue Jul 18, 2024
Merged
@voelzmo voelzmo mentioned this issue Oct 24, 2024
Closed
@gardener-robot gardener-robot added the status/closed Issue is closed (either delivered or triaged) label Nov 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@elankath elankath

Labels
area/auto-scaling Auto-scaling (CA/HPA/VPA/HVPA, predominantly control plane, but also otherwise) related kind/enhancement Enhancement, improvement, extension platform/aws Amazon web services platform/infrastructure status/closed Issue is closed (either delivered or triaged)
Projects
None yet
Milestone
No milestone
2 participants
@elankath @gardener-robot