Skip to content

add consumer autoscaling by RabbitMQ queue backlog declared in deploy/consumers.yaml - #84

Open
tommyguccis wants to merge 6 commits into
mainfrom
tk-consumer-autoscaling
Open

tommyguccis wants to merge 6 commits into
mainfrom
tk-consumer-autoscaling

Conversation

@tommyguccis

Copy link
Copy Markdown

No description provided.

Tomáš Kučera added 6 commits September 11, 2026 06:32
…on_resource from create_consumer_manifests
… merge and generate processes, expected-error.txt

- exit codes of the generation and of kustomize build were ignored, so --update recorded a broken output as expected
- drop the fallback to the old --load_restrictor flag, it masked the real kustomize error
- a scenario with expected-error.txt must fail during generation with every line of the file in the output
…/consumers.yaml

- a consumer with an autoscaling block gets a HorizontalPodAutoscaler on the external metric rabbitmq_queue_backlog when ENABLE_CONSUMER_AUTOSCALING=true
- consumers are declared either in DEFAULT_CONSUMERS or in the file, not both
…loy/consumers.yaml

- the runner copies a scenario's consumers.yaml into the mock project and checks invariants of the generated consumer manifests independently of the expected files, which --update records as they are
…te-application apply

- kubectl apply does not prune, a stale autoscaler kept overriding the static replicas
- the cleanup needs list and delete permissions on horizontalpodautoscalers
@tommyguccis
tommyguccis force-pushed the tk-consumer-autoscaling branch from ecb6b34 to 66cd1f9 Compare September 11, 2026 07:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant