Example of defining scheduled scaling for Prometheus #10097
Draft
+556
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Scheduled Scaling VPA defines a Vertical Pod Autoscaler (zVPA) resource which is an enriched version of the upstream VPA that adds the ability to change scaling based on Scaling Schedules.
An example zVPA looks like this:
The resource is combined with a simple controller that can read zVPA resources and generate/update VPA resources. If a referenced schedule is active it will use the resourcePolicy of the respective schedule, otherwise it will use the default resourcePolicy.
This PR showcases how to use this for Prometheus to scale based on central events.