Support autoscaling with KEDA #1042
Open
+2,303
−1,031
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
roypaulin
requested review from
cchen-vertica,
fenic-fawkes,
HaoYang0000,
qindotguan and
LiboYu2
as code owners
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
KEDA (Kubernetes-based Event Driven Autoscaling) is an open-source that allows for fine-grained autoscaling (including to/from zero) for event driven Kubernetes workloads. This PR integrates KEDA's ScaledObject to the VerticaAutoscaler CR. Now users can pick which autoscaler to use (scaledObject/hpa).
API changes were made now the customAutoscaler field has 3 subfields: type, hpa and scaledObject. When type is "HPA", scaledObject must be set with the metric's definition. The metric can either be cpu/mem or a prometheus metric.
Anew test case was added to scale based on a scaledObject.