feat(kube): add KEDA event-driven autoscaler operator#7605
Merged
Conversation
Deploys KEDA 2.19.0 (event-driven autoscaler) to the keda namespace. Follows the CNPG multi-source Helm pattern with pinned version and values override from repo. Added to root kustomization alongside other platform operators. KEDA enables autoscaling workloads based on external events (Redis queue depth, Kafka lag, Prometheus metrics) instead of CPU/memory. Primary use case: scaling n8n-worker based on Bull queue length. Ref #7590
Contributor
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Ref #7590
Summary
kustomization.yamlalongside other platform operatorskedanamespaceWhat KEDA enables
KEDA extends Kubernetes autoscaling beyond CPU/memory to support event-driven triggers:
Files
apps/kube/keda/application.yaml— ArgoCD Application (Helm chart pinned to 2.19.0)apps/kube/keda/manifests/values.yaml— Helm values (resources, security, monitoring)apps/kube/kustomization.yaml— Addedkeda/application.yamlto resourcesConfiguration highlights
Next steps (after merge + deploy)
kubectl get pods -n kedakubectl get crd | grep kedaScaledObjectfor n8n-worker targeting Redis Bull queue depthTest plan
kubectl apply --dry-run=clientpasses for application.yaml