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.
Signed-off-by: Ryan Karg rwkarg@gmail.com
Added an additional trigger for RabbitMQ scaling on
publishRate
.This allows for higher throughput workloads to scale based on the incoming message rate. This is useful because the message backlog does not often correlate with the desired instance count.
Both
publishRate
andqueueLength
triggers can be specified on a single ScaledObject. I would imagine the normal case would be to use both of these triggers.Checklist
[ ] A PR is opened to update our Helm chart (repo) (if applicable, ie. when deployment manifests are modified)publishRate
trigger keda-docs#388Fixes #1643