Azure Kubernetes Service
An Azure service that provides serverless Kubernetes, an integrated continuous integration and continuous delivery experience, and enterprise-grade security and governance.
thank you so much!
Kubernetes/KEDA
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(3.2, 37%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EED%3C/text%3E%3C/svg%3E)
Er, Dilber
1
Reputation point
how can I scale down pods to 0 and back up on a schedule in Kubernetes
Azure Kubernetes Service
3 answers
Sort by: Most helpful
-
Er, Dilber 1 Reputation point
2021-08-16T11:49:36.9+00:00 Thank you for the response. Should it be in conjunction with the API-initiated Eviction? or Cron Scaler is enough? so can I scale down the pods in the resource to 0 at 9 pm and back up at 8 am? When it is up, it will still have the ability to auto-scale when the app is needed, right? I'm asking to learn. Thank you!
-
SRIJIT-BOSE-MSFT 4,346 Reputation points Microsoft Employee Moderator2021-08-18T01:01:48.987+00:00 @Er, Dilber , API-initiated eviction is the process by which you use the Eviction API to create an
Evictionobject that triggers graceful pod termination. If I am not mistaken your intent is not to evict pods from node but essentially to scale the application. In that case, I believe, the Cron Scaler mentioned earlier should be enough. There can be two (or more) seperatespec.triggersin theScaledObjectresource - one to scale down the application todesiredReplicas: "0"between a definedstartandendtime (around 9 pm in your case); the other to scale up to the appropriatedesiredReplicasvalue between it's own definedstartandendtime (around 8 am in your case) [contd] -
SRIJIT-BOSE-MSFT 4,346 Reputation points Microsoft Employee Moderator
2021-08-18T01:05:16.303+00:00 When it is up, it will still have the ability to auto-scale when the app is needed, right?
KEDA allows you to use multiple triggers as part of the same
ScaledObjectorScaledJob.By doing this, your autoscaling becomes better:
- All your autoscaling rules are in one place
- You will not have multiple
ScaledObject's orScaledJob's interfering with each other
KEDA will start scaling as soon as when one of the triggers meets the criteria. Horizontal Pod Autoscaler (HPA) will calculate metrics for every scaler and use the highest desired replica count to scale the workload to.
NOTE: You can find all supported triggers here.
Sign in to comment -
-
SRIJIT-BOSE-MSFT 4,346 Reputation points Microsoft Employee Moderator
2021-08-16T04:11:32.73+00:00 @Er, Dilber , thank you for your question.
You can use the Cron Scaler available for KEDA to scale applications based on a cron schedule. Trigger Specification and Example are mentioned in the link shared.
----------
Disclaimer: This response contains a reference to a third-party World Wide Web site. Microsoft is providing this information as convenient to you. Microsoft does not control these sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there.
There are inherent dangers in the use of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet.----------
Hope this helps.
Please "Accept as Answer" if it helped, so that it can help others in the community looking for help on similar topics.