From 4fbceb8b5e1e8ff71c69f14af55a926202c1d881 Mon Sep 17 00:00:00 2001 From: Derek Date: Sun, 15 Nov 2026 11:49:14 +1100 Subject: [PATCH] docs(keda): link the dfe-infra autoscaling pages The scaling page named two dfe-infra pages as bare paths, which the doc-paths check reads as engine paths that do not exist. Link them on GitHub instead. --- docs/deployment/keda-scaling.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/deployment/keda-scaling.md b/docs/deployment/keda-scaling.md index 9d622af1..a25873ae 100644 --- a/docs/deployment/keda-scaling.md +++ b/docs/deployment/keda-scaling.md @@ -24,7 +24,7 @@ The broker autoscaler renders only for `kafka.provider: strimzi`, so Redpanda br DFE sizes ClickHouse and doesn't autoscale it. The official operator has no autoscaler: scaling is an edit to `spec.replicas` or `spec.shards`, and a new shard takes new writes only, because the operator moves no existing rows ([operator scaling](https://clickhouse.com/docs/products/kubernetes-operator/guides/scaling)). Autoscaling it may come if a paying customer needs it. -Nodes are the platform's job. KEDA adds pods, and on AWS Karpenter adds the nodes they need. On-premises DFE ships no node autoscaler, so the node pool is sized for the peak (dfe-infra `docs/autoscaling.md` and `docs/deployment/node-autoscaling.md`). +Nodes are the platform's job. KEDA adds pods, and on AWS Karpenter adds the nodes they need. On-premises DFE ships no node autoscaler, so the node pool is sized for the peak (dfe-infra [autoscaling](https://github.com/hyperi-io/dfe-infra/blob/main/docs/autoscaling.md) and [node autoscaling](https://github.com/hyperi-io/dfe-infra/blob/main/docs/deployment/node-autoscaling.md)). ## The two triggers