Body: <p>We had a fun issue yesterday and today where after a restart of some nodes, we ended up with more or less every pod on one server.  After some research, it seems like most of the solutions for this issue are either manual or rely on something outside AKS to handle it.  </p>
  
  <p>Is there a way within AKS to handle the following:  </p>
  
  <ol>
  <li>Balance pods across nodes regularly  </li>
  <li>Ensure that multiple pods of the same service are not on the same node where possible.</li>
  </ol>
  
Comments: CC BY-SA 4.0
Comments: 2019-10-16T15:02:50.390Z
Comments: Do you mean a tool directly within AKS and not using any other AWS services?
Comments: Wesley Rolnick
Comments: CC BY-SA 4.0
Comments: 2019-10-16T15:55:31.220Z
Comments: @WesleyRolnick Ideally something within Azure.  The concern with adding a lot of extra 3rd party things is potential breakage when something changes, but if that's our only option, then we'll go with that.
Comments: Marshall Tigerus
Comments: CC BY-SA 4.0
Comments: 2019-10-16T16:05:19.083Z
Comments: I misread and thought this was AWS not Azure.  Is a solution that adds more Azure services acceptable or are you trying to accomplish everything directly within AKS?
Comments: Wesley Rolnick
Comments: CC BY-SA 4.0
Comments: 2019-10-16T18:08:35.270Z
Comments: @WesleyRolnick Adding additional Azure services would be fine
Comments: Marshall Tigerus
Tags: <kubernetes><azure><azure-kubernetes-service>
Title: Keeping Pods Balanced Across Nodes in AKS
UserDisplayName: Marshall Tigerus
ThreadText: # Keeping Pods Balanced Across Nodes in AKS
  
  (Asked by: username_0 on 2019-10-16)
  
  We had a fun issue yesterday and today where after a restart of some nodes, we ended up with more or less every pod on one server. After some research, it seems like most of the solutions for this issue are either manual or rely on something outside AKS to handle it.
  
  Is there a way within AKS to handle the following:
  
  1. Balance pods across nodes regularly
  2. Ensure that multiple pods of the same service are not on the same node where possible.
  
  **Tags:** kubernetes, azure, azure-kubernetes-service
  
  > **Comments:**
  > **username_1**: Do you mean a tool directly within AKS and not using any other AWS services?  
  > **username_0**: @username_1 Ideally something within Azure.  The concern with adding a lot of extra 3rd party things is potential breakage when something changes, but if that's our only option, then we'll go with that.  
  > **username_1**: I misread and thought this was AWS not Azure.  Is a solution that adds more Azure services acceptable or are you trying to accomplish everything directly within AKS?  
  > **username_0**: @username_1 Adding additional Azure services would be fine  
  
  ---
  
  ## 0 answers
  
  