docs(install-keda): add tip pointing to the SleakOps KEDA Addon

content/docs/en/cluster/addons/keda.mdx

@@ -164,6 +164,97 @@ spec:
 For the full catalogue of triggers (Kafka, Redis, Prometheus, cron, NATS, MongoDB, …) refer to the [KEDA Scalers documentation <FiExternalLink/>](https://keda.sh/docs/2.19/scalers/).
 </details>
 
+<details>
+<summary>
+### How do I deploy `ScaledObject` manifests through SleakOps?
+</summary>
+You can deliver `ScaledObject` (and `TriggerAuthentication`) manifests to your Cluster without leaving the SleakOps console. Two paths are available — pick based on where the manifest needs to live.
+
+**Option 1 — KEDA addon Custom Values (`extraObjects`, cluster-scoped)**
+
+The upstream KEDA chart exposes an `extraObjects` list that ships any K8s manifest alongside the operator. Open the KEDA addon's detail drawer, toggle **Enable Custom Values**, and paste the YAML:
+
+```yaml
+extraObjects:
+  - apiVersion: keda.sh/v1alpha1
+    kind: ClusterTriggerAuthentication
+    metadata:
+      name: aws-irsa
+    spec:
+      podIdentity:
+        provider: aws
+  - apiVersion: keda.sh/v1alpha1
+    kind: ScaledObject
+    metadata:
+      name: order-worker-scaler
+      namespace: my-app
+    spec:
+      scaleTargetRef:
+        name: order-worker
+      minReplicaCount: 0
+      maxReplicaCount: 20
+      triggers:
+        - type: aws-sqs-queue
+          authenticationRef:
+            kind: ClusterTriggerAuthentication
+            name: aws-irsa
+          metadata:
+            queueURL: https://sqs.us-east-1.amazonaws.com/123456789012/orders
+            queueLength: "10"
+            awsRegion: us-east-1
+```
+
+These resources are owned by the KEDA addon release, which makes this the right path for **cluster-scoped resources** (`ClusterTriggerAuthentication`) and for any `ScaledObject` whose target namespace you set explicitly. Editing the YAML and clicking **Update** re-applies the set in place.
+
+**Option 2 — Project Chart Configuration (namespace-scoped, per-Project)**
+
+When the `ScaledObject` should live in the same namespace as the Workload it scales, deliver it through `Project > Settings > Chart Configuration`. The **Templates** field accepts raw Helm template YAML rendered as part of the Project's release, so `{{ .Values.global.namespace }}` resolves to the right Environment automatically:
+
+```yaml
+apiVersion: keda.sh/v1alpha1
+kind: ScaledObject
+metadata:
+  name: order-worker-scaler
+  namespace: {{ .Values.global.namespace }}
+spec:
+  scaleTargetRef:
+    name: order-worker-deployment
+  minReplicaCount: 0
+  maxReplicaCount: 20
+  pollingInterval: 30
+  cooldownPeriod: 300
+  triggers:
+    - type: aws-sqs-queue
+      authenticationRef:
+        name: keda-aws-trigger-auth
+      metadata:
+        queueURL: https://sqs.us-east-1.amazonaws.com/123456789012/orders
+        queueLength: "10"
+        awsRegion: us-east-1
+        identityOwner: operator
+---
+apiVersion: keda.sh/v1alpha1
+kind: TriggerAuthentication
+metadata:
+  name: keda-aws-trigger-auth
+  namespace: {{ .Values.global.namespace }}
+spec:
+  podIdentity:
+    provider: aws
+```
+
+<Zoom overlayBgColorEnd="rgba(255, 255, 255, 0.8)">
+  <img
+    src={require("./keda/keda-chartconfig-scaledobject.png").default}
+    alt="keda-chartconfig-scaledobject"
+  />
+</Zoom>
+
+With **Deploy?** toggled on, clicking **Apply changes** rolls out a new deployment that applies the manifest to the Project's namespace — the right path for app-specific scaling rules that should follow the Project across Environments.
+
+For a worked walk-through, see the [Install KEDA tutorial](/tutorial/install-keda).
+</details>
+
 <details>
 <summary>
 ### Can I customize the KEDA deployment?

content/docs/es/cluster/addons/keda.mdx

@@ -164,6 +164,97 @@ spec:
 Para el catálogo completo de triggers (Kafka, Redis, Prometheus, cron, NATS, MongoDB, …) consultá la [documentación de KEDA Scalers <FiExternalLink/>](https://keda.sh/docs/2.19/scalers/).
 </details>
 
+<details>
+<summary>
+### ¿Cómo aplico manifiestos de `ScaledObject` desde SleakOps?
+</summary>
+Podés entregar manifiestos de `ScaledObject` (y `TriggerAuthentication`) a tu Clúster sin salir de la consola de SleakOps. Hay dos caminos — elegí en base a dónde tiene que vivir el manifiesto.
+
+**Opción 1 — Custom Values del addon de KEDA (`extraObjects`, scope cluster)**
+
+El Helm chart de KEDA expone una lista `extraObjects` que despliega cualquier manifiesto de K8s junto al operador. Abrí el panel de detalle del addon de KEDA, activá **Enable Custom Values**, y pegá el YAML:
+
+```yaml
+extraObjects:
+  - apiVersion: keda.sh/v1alpha1
+    kind: ClusterTriggerAuthentication
+    metadata:
+      name: aws-irsa
+    spec:
+      podIdentity:
+        provider: aws
+  - apiVersion: keda.sh/v1alpha1
+    kind: ScaledObject
+    metadata:
+      name: order-worker-scaler
+      namespace: my-app
+    spec:
+      scaleTargetRef:
+        name: order-worker
+      minReplicaCount: 0
+      maxReplicaCount: 20
+      triggers:
+        - type: aws-sqs-queue
+          authenticationRef:
+            kind: ClusterTriggerAuthentication
+            name: aws-irsa
+          metadata:
+            queueURL: https://sqs.us-east-1.amazonaws.com/123456789012/orders
+            queueLength: "10"
+            awsRegion: us-east-1
+```
+
+Estos recursos quedan asociados al release del addon de KEDA, lo que hace de este el camino correcto para **recursos cluster-scoped** (`ClusterTriggerAuthentication`) y para cualquier `ScaledObject` cuyo namespace destino definas explícitamente en el manifiesto. Editar el YAML y hacer clic en **Update** vuelve a aplicar el conjunto in-place.
+
+**Opción 2 — Chart Configuration del Proyecto (scope namespace, por Proyecto)**
+
+Cuando el `ScaledObject` tiene que vivir en el mismo namespace que el Workload que escala, entregalo a través de `Project > Settings > Chart Configuration`. El campo **Templates** acepta YAML de templates de Helm que se renderiza como parte del release del Proyecto, así que `{{ .Values.global.namespace }}` resuelve al Environment correcto automáticamente:
+
+```yaml
+apiVersion: keda.sh/v1alpha1
+kind: ScaledObject
+metadata:
+  name: order-worker-scaler
+  namespace: {{ .Values.global.namespace }}
+spec:
+  scaleTargetRef:
+    name: order-worker-deployment
+  minReplicaCount: 0
+  maxReplicaCount: 20
+  pollingInterval: 30
+  cooldownPeriod: 300
+  triggers:
+    - type: aws-sqs-queue
+      authenticationRef:
+        name: keda-aws-trigger-auth
+      metadata:
+        queueURL: https://sqs.us-east-1.amazonaws.com/123456789012/orders
+        queueLength: "10"
+        awsRegion: us-east-1
+        identityOwner: operator
+---
+apiVersion: keda.sh/v1alpha1
+kind: TriggerAuthentication
+metadata:
+  name: keda-aws-trigger-auth
+  namespace: {{ .Values.global.namespace }}
+spec:
+  podIdentity:
+    provider: aws
+```
+
+<Zoom overlayBgColorEnd="rgba(255, 255, 255, 0.8)">
+  <img
+    src={require("./keda/keda-chartconfig-scaledobject.png").default}
+    alt="keda-chartconfig-scaledobject"
+  />
+</Zoom>
+
+Con **Deploy?** activado, hacer clic en **Apply changes** dispara un nuevo deployment que aplica el manifiesto en el namespace del Proyecto — el camino correcto para reglas de escalado específicas de la aplicación que tienen que seguir al Proyecto entre Environments.
+
+Para un walk-through completo, mirá el [tutorial de Instalar KEDA](/tutorial/install-keda).
+</details>
+
 <details>
 <summary>
 ### ¿Puedo personalizar el deployment de KEDA?

content/tutorials/en/install-keda.mdx

@@ -20,6 +20,12 @@ import { FiExternalLink } from "react-icons/fi";
 
 Learn how to install KEDA (Kubernetes Event-Driven Autoscaling) on your cluster using different methods. KEDA allows you to automatically scale your applications based on events and custom metrics.
 
+:::tip Install via the SleakOps Addon
+If your cluster is managed by SleakOps, you can install KEDA in one click from the **Addons** section of your cluster — SleakOps deploys the operator, the metrics adapter, the admission webhooks, and wires up the IAM role via IRSA for the AWS scalers (SQS, CloudWatch, DynamoDB Streams, Kinesis, …).
+
+See the [KEDA Addon documentation](/docs/cluster/addons/keda) for full installation steps, AWS policy configuration, and `ScaledObject` examples.
+:::
+
 ## Installation Methods
 
 ### Using Lens Interface (option 1)

content/tutorials/es/install-keda.mdx

@@ -20,6 +20,12 @@ import { FiExternalLink } from "react-icons/fi";
 
 Aprende cómo instalar KEDA (Kubernetes Event-Driven Autoscaling) en tu clúster usando diferentes métodos. KEDA permite escalar automáticamente tus aplicaciones basándote en eventos y métricas personalizadas.
 
+:::tip Instalá vía el Addon de SleakOps
+Si tu clúster está gestionado por SleakOps, podés instalar KEDA con un solo clic desde la sección **Addons** de tu clúster — SleakOps despliega el operador, el metrics adapter, los admission webhooks, y configura el rol de IAM vía IRSA para los scalers de AWS (SQS, CloudWatch, DynamoDB Streams, Kinesis, …).
+
+Mirá la [documentación del Addon de KEDA](/docs/cluster/addons/keda) para los pasos completos de instalación, configuración de policies de AWS, y ejemplos de `ScaledObject`.
+:::
+
 ## Métodos de Instalación
 
 ### Usando la interfaz de Lens (opción 1)