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

Add Node Pool Support #287

Closed
derekperkins opened this Issue Apr 3, 2018 · 40 comments

Comments

Projects
None yet
@derekperkins
Copy link
Contributor

derekperkins commented Apr 3, 2018

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?

image

@sauryadas

This comment has been minimized.

Copy link
Member

sauryadas commented Apr 5, 2018

In the roadmap, about 6 months

@sauryadas sauryadas added the roadmap label Apr 5, 2018

@derekperkins

This comment has been minimized.

Copy link
Contributor Author

derekperkins commented Apr 5, 2018

Thanks for the heads up.

@lawgorht

This comment has been minimized.

Copy link

lawgorht commented Apr 8, 2018

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?

@lawgorht

This comment has been minimized.

Copy link

lawgorht commented May 15, 2018

@sauryadas Could you tell us if it will be possible to remove Nodepools?
thank you!

@sauryadas

This comment has been minimized.

Copy link
Member

sauryadas commented May 15, 2018

@judy

This comment has been minimized.

Copy link

judy commented Jun 15, 2018

+1 for this. I'm also interested in using different node pools for security reasons, like single tenancy for Vault.

@marcel-dempers

This comment has been minimized.

Copy link

marcel-dempers commented Aug 8, 2018

Hi all, any update on this ? Based on this thread we are 2 months away from node pool support ?

@agolomoodysaada

This comment has been minimized.

Copy link
Contributor

agolomoodysaada commented Aug 10, 2018

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.

@agolomoodysaada

This comment has been minimized.

Copy link
Contributor

agolomoodysaada commented Aug 10, 2018

Can we at least open up preview versions? 😭

@kvolkovich-sc

This comment has been minimized.

Copy link

kvolkovich-sc commented Aug 13, 2018

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.

@agolomoodysaada

This comment has been minimized.

Copy link
Contributor

agolomoodysaada commented Aug 13, 2018

@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

@alanjcastonguay

This comment has been minimized.

Copy link

alanjcastonguay commented Aug 13, 2018

It also doesn't work for mixing node types (eg, one node pool has GPUs).

@gabrielmcf

This comment has been minimized.

Copy link

gabrielmcf commented Aug 29, 2018

Any new on this issue? Is there a beta version already? Still planned to october?

@kitgary

This comment has been minimized.

Copy link

kitgary commented Sep 1, 2018

Any update on this? I really need it for production.

@sauryadas

This comment has been minimized.

Copy link
Member

sauryadas commented Sep 1, 2018

End of Oct is still the ETA .. Thanks for your patience.

@ormico

This comment has been minimized.

Copy link

ormico commented Sep 25, 2018

T - 36 days and counting

@ormico

This comment has been minimized.

Copy link

ormico commented Oct 1, 2018

@jmajoor

This comment has been minimized.

Copy link

jmajoor commented Oct 5, 2018

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.

@sauryadas

This comment has been minimized.

Copy link
Member

sauryadas commented Oct 5, 2018

the eventual goal is to support hybrid clusters but there is no ETA yet for windows support in AKS. Sorry.

@arwkmd

This comment has been minimized.

Copy link

arwkmd commented Oct 22, 2018

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.

@btok

This comment has been minimized.

Copy link

btok commented Oct 28, 2018

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 !

@sauryadas

This comment has been minimized.

Copy link
Member

sauryadas commented Oct 29, 2018

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.

@przemolb

This comment has been minimized.

Copy link

przemolb commented Oct 30, 2018

@sauryadas can you please tell us what is the reason to delay it ?

@sauryadas

This comment has been minimized.

Copy link
Member

sauryadas commented Oct 31, 2018

@przemolb Currently we are focused on fixing any existing issues and keep the QoS high before we roll out new features ...

@przemolb

This comment has been minimized.

Copy link

przemolb commented Oct 31, 2018

@sauryadas hire more people ;-)

@damienwebdev

This comment has been minimized.

Copy link

damienwebdev commented Nov 7, 2018

@przemolb https://en.wikipedia.org/wiki/The_Mythical_Man-Month

Azure AKS team... I appreciate your decision to delay to maintain quality. Thank you.

@derekperkins

This comment has been minimized.

Copy link
Contributor Author

derekperkins commented Nov 7, 2018

maintain quality

That presumes that the existing offering is actually GA quality.

@kitgary

This comment has been minimized.

Copy link

kitgary commented Nov 8, 2018

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.

@seanmck

This comment has been minimized.

Copy link
Collaborator

seanmck commented Dec 6, 2018

This is under active development. We will update progress here:

https://feedback.azure.com/forums/914020-azure-kubernetes-service-aks/suggestions/34917127-support-multiple-node-pool

@seanmck seanmck closed this Dec 6, 2018

@przemolb

This comment has been minimized.

Copy link

przemolb commented Dec 6, 2018

@seanmck why this is closed if it is still under development ?

@agolomoodysaada

This comment has been minimized.

Copy link
Contributor

agolomoodysaada commented Dec 6, 2018

Closing makes no sense to me until this is resolved

@mnadeau2

This comment has been minimized.

Copy link

mnadeau2 commented Dec 6, 2018

Can you disclose some details about the feature ?

  • Will it be possible to have node in multiple region ?
  • Will it be possible to have diferent size of pool ?
@gabrielmcf

This comment has been minimized.

Copy link

gabrielmcf commented Dec 10, 2018

Is there a criteria to close an issue @seanmck? Why it would be closed if the issue was not solved?

@seanmck

This comment has been minimized.

Copy link
Collaborator

seanmck commented Dec 11, 2018

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:

  • No, you will not be able to have node pools in different regions attached to the same AKS cluster.
  • Yes, it will possible to have different pool sizes.
@albertocsm

This comment has been minimized.

Copy link

albertocsm commented Dec 13, 2018

+1

@dbuschman7

This comment has been minimized.

Copy link

dbuschman7 commented Jan 21, 2019

It is now 2019, any update of a deployment/rollout date for each region?

@yas51ne

This comment has been minimized.

Copy link

yas51ne commented Jan 29, 2019

+1

@gabrielmcf

This comment has been minimized.

Copy link

gabrielmcf commented Feb 13, 2019

@sauryadas, any update on this feature? Is it still predicted for this quarter?

@trdavidson

This comment has been minimized.

Copy link

trdavidson commented Feb 21, 2019

Deleted by moderator.

@Azure Azure locked as too heated and limited conversation to collaborators Feb 21, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.