ghost
commented
3 years ago 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: 1) If this case is urgent, please open a Support Request so that our 24/7 support team may help you faster. 2) Please abide by the AKS repo Guidelines and Code of Conduct. 3) If you're having an issue, could it be described on the AKS Troubleshooting guides or AKS Diagnostics? 4) Make sure your subscribed to the AKS Release Notes to keep up to date with all that's new on AKS. 5) 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. 6) If you have a question, do take a look at our AKS FAQ. We place the most common ones there!
justindavies
microsoft-github-policy-service[bot]
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:
kubectl version):