AKS
AKS copied to clipboard
[Autoscaling] Support for node PATCH operations on creation and scaling
What happened: We have a use-case for extending resources with our own property to limit the amount of services we schedule per node. Ref.: Assign Extended Resources to a Container, this seems to be stable in release v1.21 of kubernetes, but it would require patching the node after it exists. Ref.: Advertise Extended Resources for a Node
What you expected to happen: The ability for adding these extensions to node pools, so that when autoscaling happens they're already added.
How to reproduce it (as minimally and precisely as possible): To be honest, I've not had time to test this, but looking at the terraform provider and azure CLI documentation I can't find any reference to this being supported at this time, as we currently run on 1.18.x - 1.20.x.
Anything else we need to know?:
Environment:
- Kubernetes version (use
kubectl version
): - Size of cluster (how many worker nodes are in the cluster?)
- General description of workloads in the cluster (e.g. HTTP microservices, Java app, Ruby on Rails, machine learning, etc.)
Mix of microservices (spring boot) and per-tenant java application (high mem/cpu workload)
- Others:
Hi kbjerke, AKS bot here :wave: Thank you for posting on the AKS Repo, I'll do my best to get a kind human from the AKS team to assist you.
I might be just a bot, but I'm told my suggestions are normally quite good, as such:
- If this case is urgent, please open a Support Request so that our 24/7 support team may help you faster.
- Please abide by the AKS repo Guidelines and Code of Conduct.
- If you're having an issue, could it be described on the AKS Troubleshooting guides or AKS Diagnostics?
- Make sure your subscribed to the AKS Release Notes to keep up to date with all that's new on AKS.
- Make sure there isn't a duplicate of this issue already reported. If there is, feel free to close this one and '+1' the existing issue.
- If you have a question, do take a look at our AKS FAQ. We place the most common ones there!
Triage required from @Azure/aks-pm
Action required from @Azure/aks-pm
Hi thanks for raising this, I’ll take a look and will keep this issue updated
Action required from @Azure/aks-pm
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads