Skip to content

SLEAK-5570: support scope page #222

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
agustinoli wants to merge 2 commits into
base: develop
Choose a base branch
from
Open

SLEAK-5570: support scope page #222

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e19ee60
docs(support): add support scope page (SLEAK-5570)
agustinoli Jul 2, 2026
b94da24
docs(support): fill in both sides of the responsibility table (SLEAK-…
agustinoli Jul 8, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion content/docs/en/responsability-model.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,4 +9,6 @@ We transparently utilize all AWS services, which means the responsibility extend
To safeguard your data and ensure it doesn't get lost due to potential service disruptions, it's advisable to have backup policies in place. Currently, we don't support backups for our dependencies (RDS, S3, RabbitMQ, etc.). To set this up, you can access via your AWS client and define your backup policies.

[Learn more about AWS's Shared Responsibility Model]
(https://aws.amazon.com/compliance/shared-responsibility-model/)<FiExternalLink />
(https://aws.amazon.com/compliance/shared-responsibility-model/)<FiExternalLink />

For what's covered by SleakOps support specifically, see [Support](/docs/support).
35 changes: 35 additions & 0 deletions content/docs/en/support.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,35 @@
---
sidebar_position: 18
---

# Support

If you run into an issue or have a question, the fastest way to get help is through **Support**, in the main sidebar of the console — it combines an AI-powered chat with support tickets for your account. Before reaching out, it's worth a quick search here in the docs: most day-to-day questions are already answered in a tutorial or FAQ.

## What our support covers

- Questions about how to do something in SleakOps.
- Infrastructure issues on resources provisioned through the platform (clusters, environments, dependencies, addons).
- Help updating or scaling resources that SleakOps provisioned for you.

## Where to look first

For a few common questions, the fastest answer is one you can get yourself, right now:

- **Something's wrong in your application or its code** — that's owned and debugged by your own team; SleakOps manages the infrastructure your application runs on, not the application itself.
- **The application feels slow** — start with [Kubecost](/docs/cluster/addons/kubecost) and [Prometheus](/docs/cluster/addons/prometheus) to see what your workloads are actually using, before assuming it's an infrastructure problem.
- **Questions about your Dockerfile or build configuration** — see [Chart Dependencies](/docs/project/chart/chart_dependencies) for what's supported out of the box.
- **You want to understand or reduce your AWS spend** — see [AWS Cost Optimization Strategies](/tutorial/optimize-aws-costs) for concrete ways to bring it down.
- **Choosing AWS services or designing your architecture** — see the [Responsibility Model](/docs/responsability-model) below and [AWS's own documentation](https://docs.aws.amazon.com/) for guidance; these decisions are yours to make for your application.

## Responsibility at a glance

| | SleakOps | You |
|---|---|---|
| **Platform & infrastructure** | Clusters, networking, provisioning, and the resources SleakOps creates for you | Configure environment variables, define resource requirements, and monitor usage |
| **Your application** | Provide runtime environment, CI/CD pipelines capabilities, and observability tools (logs/metrics) | Your code, its dependencies, and its performance |
| **Data & backups** | Automated execution, secure storage, and restoration capabilities. | Backup policies for your dependencies (see [Responsibility Model](/docs/responsability-model)) |
Comment on lines +29 to +31

@coderabbitai coderabbitai Bot Jul 15, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🗄️ Data Integrity & Integration | 🟡 Minor | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

printf '\n== support.mdx (en) ==\n'
sed -n '1,120p' content/docs/en/support.mdx

printf '\n== support.mdx (es) ==\n'
sed -n '1,120p' content/docs/es/support.mdx

printf '\n== responsibility model references ==\n'
rg -n "backup|restore|restoration|RDS|S3|RabbitMQ|dependenc" content/docs -S

Repository: sleakops/docs

Length of output: 50370

🏁 Script executed:

#!/bin/bash
set -euo pipefail

printf '\n== responsibility model (en) ==\n'
cat -n content/docs/en/responsability-model.mdx | sed -n '1,120p'

printf '\n== backup-related mentions in support + responsibility ==\n'
rg -n "backup|restoration|restore|dependencies \(RDS, S3, RabbitMQ|don't support backups|not support backups" content/docs/en/support.mdx content/docs/en/responsability-model.mdx -S

Repository: sleakops/docs

Length of output: 1664

Ajustad la fila de “Data & backups” en ambas versiones
Ahora mismo la tabla le atribuye a SleakOps “restoration capabilities”, pero el modelo de responsabilidad dice que los backups de las dependencias (RDS, S3, RabbitMQ, etc.) los gestiona el cliente. Alinead ese texto para que no se contradigan.

📍 Affects 2 files
  • content/docs/en/support.mdx#L29-L31 (this comment)
  • content/docs/es/support.mdx#L29-L31
🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@content/docs/en/support.mdx` around lines 29 - 31, Update the “Data &
backups” row in both content/docs/en/support.mdx (lines 29-31) and
content/docs/es/support.mdx (lines 29-31) so it no longer attributes backup or
restoration of customer-managed dependencies to SleakOps; align the
responsibility wording with the Responsibility Model, stating that the client
manages backups for dependencies such as RDS, S3, and RabbitMQ.


## Still not sure?

If you're not sure whether something is covered, just ask — reach out through **Support** and we'll point you in the right direction.
4 changes: 3 additions & 1 deletion content/docs/es/responsability-model.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,4 +9,6 @@ Utilizamos de manera transparente todos los servicios de AWS, lo que implica que
Para proteger tus datos y asegurarte de que no se pierdan debido a posibles interrupciones en los servicios, es recomendable contar con políticas de respaldo. Actualmente, no ofrecemos soporte para respaldos de nuestras dependencias (RDS, S3, RabbitMQ, etc.). Para configurarlos, puedes acceder a través de tu cliente de AWS y definir tus políticas de respaldo.

[Obtén más información sobre el Modelo de Responsabilidad Compartida de AWS]
(https://aws.amazon.com/compliance/shared-responsibility-model/)<FiExternalLink />
(https://aws.amazon.com/compliance/shared-responsibility-model/)<FiExternalLink />

Para ver qué cubre específicamente el soporte de SleakOps, consulta [Soporte](/docs/support).
35 changes: 35 additions & 0 deletions content/docs/es/support.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,35 @@
---
sidebar_position: 18
---

# Soporte

Si tienes un problema o una pregunta, la forma más rápida de obtener ayuda es a través de **Support**, en la barra lateral principal de la consola — combina un chat con IA y tickets de soporte para tu cuenta. Antes de escribir, vale la pena buscar aquí en la documentación: la mayoría de las preguntas del día a día ya están respondidas en un tutorial o FAQ.

## Qué cubre nuestro soporte

- Preguntas sobre cómo hacer algo en SleakOps.
- Problemas de infraestructura en recursos provistos a través de la plataforma (clusters, ambientes, dependencias, addons).
- Ayuda para actualizar o escalar recursos que SleakOps provisionó para ti.

## Dónde mirar primero

Para algunas preguntas frecuentes, la respuesta más rápida es una que puedes conseguir tú mismo, ahora mismo:

- **Algo falla en tu aplicación o en su código** — eso lo maneja y depura tu propio equipo; SleakOps administra la infraestructura sobre la que corre tu aplicación, no la aplicación en sí.
- **La aplicación se siente lenta** — empieza por [Kubecost](/docs/cluster/addons/kubecost) y [Prometheus](/docs/cluster/addons/prometheus) para ver qué están usando realmente tus workloads, antes de asumir que es un problema de infraestructura.
- **Preguntas sobre tu Dockerfile o la configuración del build** — consulta [Chart Dependencies](/docs/project/chart/chart_dependencies) para ver qué está soportado de fábrica.
- **Quieres entender o reducir tu gasto en AWS** — consulta [Estrategias de optimización de costos en AWS](/tutorial/optimize-aws-costs) para formas concretas de bajarlo.
- **Elegir servicios de AWS o diseñar tu arquitectura** — consulta el [Modelo de Responsabilidad](/docs/responsability-model) más abajo y la [documentación propia de AWS](https://aws.amazon.com/) como guía; estas decisiones son tuyas para tu aplicación.

## Responsabilidad de un vistazo

| | SleakOps | Tú |
|---|---|---|
| **Plataforma e infraestructura** | Clusters, networking, provisión, y los recursos que SleakOps crea para ti | Configurar variables de entorno, definir requisitos de recursos y monitorear el uso. |
| **Tu aplicación** | Proveer el entorno de ejecución, pipelines de CI/CD y herramientas de observabilidad (logs/métricas). | Tu código, sus dependencias y su rendimiento |
| **Datos y backups** | Ejecución automatizada, almacenamiento seguro y capacidades de restauración. | Políticas de backup de tus dependencias (ver [Modelo de Responsabilidad](/docs/responsability-model)) |

## ¿Todavía no estás seguro?

Si no estás seguro de si algo está cubierto, simplemente pregunta — escríbenos a través de **Support** y te vamos a orientar.