-
Notifications
You must be signed in to change notification settings - Fork 308
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
Multiple Node Pool Support #287
Comments
In the roadmap, about 6 months |
Thanks for the heads up. |
We are planning to move our cloudservices to a container environment. I was very impressed with the ease of use of AKS while testing it. However, the impossibility to scale the size of the VMs is a blocker at the moment (#79). Do I understand it correctly that with the future possibility of adding different nodepools it would be possible to add a new nodepool and then delete the old one without service interruption? |
@sauryadas Could you tell us if it will be possible to remove Nodepools? |
+1 for this. I'm also interested in using different node pools for security reasons, like single tenancy for Vault. |
Hi all, any update on this ? Based on this thread we are 2 months away from node pool support ? |
This is a deal breaker for us as we require running most workloads on standard VMs while CPU intensive workloads require special CPU hardware like the F series VMs. |
Can we at least open up preview versions? 😭 |
I made a manual temporary hack) Just change single node size manually to increase RAM (need more for one pod). Looks like it works normally. But I don't know what to expect after next time horizontal scaling. |
@kvolkovich-sc that doesn't work with horizontal scaling unfortunately. I tried asking Azure support for help but they said we have to wait for node pool support for this to work |
It also doesn't work for mixing node types (eg, one node pool has GPUs). |
Any new on this issue? Is there a beta version already? Still planned to october? |
Any update on this? I really need it for production. |
End of Oct is still the ETA .. Thanks for your patience. |
T - 36 days and counting |
cool. k8 v1.12 released with Azure Scale Set support. must be getting close. |
Will support for multiple node pools also include the ability to have one pool of Linux nodes and another pool of Windows nodes. Currently the only option for windows containers on AKS is through virtual-kubelets, which uses ACI. There are too many limitations in using ACI and windows containers. These restrictions shouldn't be necessary if you can setup a pool of windows nodes. |
the eventual goal is to support hybrid clusters but there is no ETA yet for windows support in AKS. Sorry. |
There is a problem with iteration over pools in all templates used to generate ARM templates. See Azure/acs-engine#3102. AKS uses ACS-Engine under hood. |
Hi @sauryadas ! Can you please give us current status of the ETA of node pools ? |
node pools has been delayed by a quarter and will now come in the 1st quarter of 2019. Apologies for the delay. I will keep you posted if we get it in earlier. |
@sauryadas can you please tell us what is the reason to delay it ? |
@przemolb Currently we are focused on fixing any existing issues and keep the QoS high before we roll out new features ... |
@sauryadas hire more people ;-) |
Multiple node pools are now in public preview: https://github.com/Azure/AKS/blob/master/previews.md#multiple-node-pools |
This feature is set to GA in Q4CY19. |
This feature is now generally available, thank you everyone for your patience and feedback on this important feature. Documentation can be found at aka.ms/aks/nodepools. Closing. |
This is a tracking issue for node pool support as mentioned by @slack in #79. Node pools are shown in the UI, but without a way to add new ones. I'm wanting to add some L series nodes to my cluster to run a database, but keep using D series machines for the bulk of my workers. When are multiple node pools expected to be supported?
The text was updated successfully, but these errors were encountered: