-
Notifications
You must be signed in to change notification settings - Fork 241
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
Clean up code relating to decision_policy and forecast_policy. #3957
base: master
Are you sure you want to change the base?
Clean up code relating to decision_policy and forecast_policy. #3957
Conversation
…s gone. PAASTA-18298
…round decision_policy to be a little more accurate.
I could be convinced to drop the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the decision policy changes seem pretty safe to me - imo, it's probably fine to leave them in
(and i agree that we should probably change how bespoke autoscaling works in the future - i think that even the current owners get confused by how this works now: we've had a non-zero amount of onpoint requests from these owners where they've thought something was broken since there were no HPAs :p)
:bespoke: | ||
Allows a service author to implement their own autoscaling. | ||
This policy results in no HPA being configured. | ||
An external process should periodically decide how many replicas this service needs to run, and use the Paasta API to tell Paasta to scale. | ||
See the :ref:`How to create a custom (bespoke) autoscaling method` section for details. | ||
This is most commonly used by the Kew autoscaler. | ||
|
||
:Anything other value: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
was this meant to be Any other value:
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes
We'll need to ship a yelpsoa-configs change that stops setting
forecast_policy
before we ship this.