+### How do I deploy `ScaledObject` manifests through SleakOps? +
+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 +``` + +![keda-chartconfig-scaledobject]({require("./keda/keda-chartconfig-scaledobject.png").default})
+![autodiagnostics-demo]({require("./autodiagnostic/autodiagnostic.gif").default})
## FAQs
diff --git a/content/docs/en/powered-ai/autodiagnostic/autodiagnostic.gif b/content/docs/en/powered-ai/autodiagnostic/autodiagnostic.gif
new file mode 100644
index 000000000..6026f22dd
Binary files /dev/null and b/content/docs/en/powered-ai/autodiagnostic/autodiagnostic.gif differ
diff --git a/content/docs/en/powered-ai/conversation.mdx b/content/docs/en/powered-ai/conversation.mdx
index 56584564b..824888938 100644
--- a/content/docs/en/powered-ai/conversation.mdx
+++ b/content/docs/en/powered-ai/conversation.mdx
@@ -12,7 +12,11 @@ import { FiExternalLink } from "react-icons/fi";
Infrastructure Chat lets you ask questions about your infrastructure in plain language and get instant answers, diagnostics, and reports — without navigating dashboards or remembering command syntax.
-{/* TODO: screenshot - Support section showing the chat interface with an active conversation */}
+![infrastructure-chat-demo]({require("./conversation/conversation.gif").default})
:::caution Alpha
Infrastructure Chat is currently in **Alpha**. Core functionality is working, but the experience and available capabilities are still being refined.
diff --git a/content/docs/en/powered-ai/conversation/conversation.gif b/content/docs/en/powered-ai/conversation/conversation.gif
new file mode 100644
index 000000000..6026f22dd
Binary files /dev/null and b/content/docs/en/powered-ai/conversation/conversation.gif differ
diff --git a/content/docs/en/powered-ai/dockertron.mdx b/content/docs/en/powered-ai/dockertron.mdx
index 111b217f2..8571d0a0e 100644
--- a/content/docs/en/powered-ai/dockertron.mdx
+++ b/content/docs/en/powered-ai/dockertron.mdx
@@ -12,6 +12,12 @@ import { FiExternalLink } from "react-icons/fi";
Dockertron analyzes your repository and generates everything needed to run your application on SleakOps: production-ready Dockerfiles, a docker-compose configuration, and the full infrastructure model — no config files to write, no templates to copy.
+![dockertron-demo]({require("./dockertron/dockertron.gif").default})
+
![ai-reports-demo]({require("./dockertron/dockertron-executions.png").default})
+
![]({require("./reports/reports-page.png").default})
](https://keda.sh/docs/2.19/scalers/).
+
+