Closed derekperkins closed 5 years ago
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? thank you!
There is only one node pool support today . You cannot delete that node pool. You will need to delete the cluster itself. When we have support for multiple node pools , you will be able to delete a node pool when you have more than one node pool.
Thanks Saurya
From: lawgorht notifications@github.com Sent: Tuesday, May 15, 2018 5:15:42 AM To: Azure/AKS Cc: Saurya Das; Mention Subject: Re: [Azure/AKS] Add Node Pool Support (#287)
@sauryadashttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fsauryadas&data=02%7C01%7Csaudas%40microsoft.com%7C9771e9c166cf4458b8fd08d5ba5d9578%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636619833463752659&sdata=6TsvbX6cHa6vpYTIE10hLj6wAzzp%2Fe4eKCPE%2BMAnztM%3D&reserved=0 Could you tell us if it will be possible to remove Nodepools? thank you!
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2FAKS%2Fissues%2F287%23issuecomment-389145228&data=02%7C01%7Csaudas%40microsoft.com%7C9771e9c166cf4458b8fd08d5ba5d9578%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636619833463752659&sdata=3oIMpPCFV52Gj1aj3r9U47hiAfsVPJG1n3HEaV%2BIqq0%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAOrMb22DOsrqQSOEgbe-chpQvoEqg56Vks5tysbugaJpZM4TF8XM&data=02%7C01%7Csaudas%40microsoft.com%7C9771e9c166cf4458b8fd08d5ba5d9578%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636619833463762663&sdata=%2FdSyg9dtgq7euV1%2Bhlu%2FDH9obspVxIEqn8cw4o0arv8%3D&reserved=0.
+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.
It's also critical for migrating to VMs with larger OS disks. Otherwise, when disks are too small, the kubelet starts evicting pods due to the nodefs.available
signal.
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. https://kubernetes.io/blog/2018/09/27/kubernetes-1.12-kubelet-tls-bootstrap-and-azure-virtual-machine-scale-sets-vmss-move-to-general-availability/
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 https://github.com/Azure/acs-engine/issues/3102. AKS uses ACS-Engine under hood.
Hi @sauryadas ! Can you please give us current status of the ETA of node pools ? Would REALLY appriciate planning according to ETA on my end as its an urgent update for production env. Thanks a lot !
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 ;-)
@przemolb https://en.wikipedia.org/wiki/The_Mythical_Man-Month
Azure AKS team... I appreciate your decision to delay to maintain quality. Thank you.
maintain quality
That presumes that the existing offering is actually GA quality.
I am really disappointed. Your competitors GKE, EKS and even IBM have already supported node pool for a long time, among the most popular Kubernetes service providers, Azure also offers the least features. My company has used Azure for all projects, we need the node pool for production, and this feature has been delayed for a long time. We may change to use EKS.
This is under active development. We will update progress here:
@seanmck why this is closed if it is still under development ?
Closing makes no sense to me until this is resolved
Can you disclose some details about the feature ?
Is there a criteria to close an issue @seanmck? Why it would be closed if the issue was not solved?
My apologies. I should have been clearer about the closure. Per the readme, we are trying to keep this repo focused on issues with the existing scope of the service, while directing feature requests to the Azure Feedback Forum, which allows us to easily see the priority of various requests based on the votes received. When items are tracked there, I am closing them here to avoid duplication and keep this repo focused on bugs.
To answer the questions from @mnadeau2:
+1
It is now 2019, any update of a deployment/rollout date for each region?
+1
@sauryadas, any update on this feature? Is it still predicted for this quarter?
Deleted by moderator.
Multiple node pool support is on track for 1H2019 delivery.
Reopening to track this as a roadmap top-level item. Please remember this repository is operated under the Microsoft code of conduct (https://opensource.microsoft.com/codeofconduct/) and comments not adhering to it will be removed.
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 https://github.com/Azure/AKS/issues/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?