Click on Delete to confirm and trigger the action on SleakOps.
+ +:::info +You can't delete internal node pools (including the build pool), the last non-internal (customer) node pool in the cluster, or a node pool currently assigned to a Project Environment — reassign or remove the environment first. The cluster must also be powered on to delete a node pool. +::: diff --git a/content/docs/en/cluster/shutdown-cluster.mdx b/content/docs/en/cluster/shutdown-cluster.mdx index bebaef712..006bc3745 100644 --- a/content/docs/en/cluster/shutdown-cluster.mdx +++ b/content/docs/en/cluster/shutdown-cluster.mdx @@ -10,6 +10,8 @@ import { FiExternalLink } from "react-icons/fi"; It is the capacity to turn off all your cluster's resources at a specified scheduled time to avoid incurring costs during that time frame. When this feature is activated you will be able to turn ON or OFF your cluster at any time, even outside the scheduled time you've configured. +When your cluster turns back on, SleakOps restores the exact node pools it had before shutting down. + :::warning When your cluster is OFF, you will not be able to run any Build, Deploy or other actions that require its resources to run. ::: @@ -42,6 +44,10 @@ Below you will see a box that shows 'Generated Cron Expressions (UTC)', which di ## How can I shutdown my cluster at any time? +:::info +Manual start/stop is only available once Scheduled Shutdown has been configured for the cluster. If it hasn't, SleakOps prompts you to set up a schedule first instead of turning the cluster off. +::: + In order to shutdown a cluster, just click on the *Stop* button and confirm the action. This action can be performed just in *Active* clusters. diff --git a/content/docs/en/domain/delegation.mdx b/content/docs/en/domain/delegation.mdx index 571a4f889..c7935ef3f 100644 --- a/content/docs/en/domain/delegation.mdx +++ b/content/docs/en/domain/delegation.mdx @@ -228,40 +228,25 @@ sequenceDiagram participant ALB as AWS ALB U->>S: Create Alias: api.external.com - S-->>U: Provide Certificate Validation Records - U->>DNS: Add Validation CNAME Records - DNS-->>S: Certificate Validated ✅ + S-->>U: Reuses external.com's certificate (no validation needed) S-->>U: Provide ALB Endpoint U->>DNS: Add CNAME to ALB DNS->>ALB: Traffic Routed ALB-->>U: Service Accessible ``` -#### For SSL Certificate Validation - -1. **Sleakops provides validation records** - - You'll see CNAME records for certificate validation - - Example: - -``` -_acme-challenge.api.external.com → _validation123.acme.aws.com -``` - -2. **Add validation records to your DNS** - - Go to the hosted zone for `external.com` (in Sleakops or wherever it's managed) - - Add the CNAME records exactly as shown - - Wait for certificate validation (usually 5-15 minutes) +Since `api.external.com` is a direct subdomain of a domain Sleakops already manages in the same account, it reuses that domain's certificate — there's no separate SSL validation step. If the parent domain belongs to a different account, the alias gets its own certificate with manual validation records instead. #### For Traffic Routing -3. **Sleakops provides ALB endpoint** +1. **Sleakops provides ALB endpoint** - You'll see the ALB DNS name: ``` ALB: my-alb-123456.us-east-1.elb.amazonaws.com ``` -4. **Create CNAME record** +2. **Create CNAME record** - Go to your DNS management for `external.com` - Create a CNAME record: @@ -272,7 +257,7 @@ Value: my-alb-123456.us-east-1.elb.amazonaws.com TTL: 300 ``` -5. **Verify** +3. **Verify** - Test the domain: `curl https://api.external.com` - Should return your service response @@ -419,6 +404,17 @@ graph TD 3. Remove any conflicting DNS records 4. Wait 15-30 minutes for DNS propagation 5. Check DNS: `dig _acme-challenge.yourdomain.com` +6. If validation fails because of a CAA policy, Sleakops shows the exact CAA record to add (e.g. `0 issue "amazon.com"`) in the domain's Certificate section — add it and check again + +--- + +### Alias domain rejected when creating it + +**Issue:** Creating an alias fails with a domain format error + +**Solutions:** +1. Use a top-level domain of 6 characters or fewer (e.g. `.com`, `.io`, `.dev`) — longer TLDs aren't currently supported for aliases +2. Wildcard aliases (`*.domain.com`) aren't supported from the panel — create explicit subdomains instead --- diff --git a/content/docs/en/domain/index.mdx b/content/docs/en/domain/index.mdx index 327eede72..d2c2739bc 100644 --- a/content/docs/en/domain/index.mdx +++ b/content/docs/en/domain/index.mdx @@ -111,10 +111,10 @@ Zero-configuration domain setup. Each service automatically gets a predictable, **What Sleakops does:** ### Scenario A: Domain matches an existing hosted zone -If `external-domain.com` is already a Provider or Environment in Sleakops: -- ✅ Provides DNS records for SSL certificate validation +If the alias is a direct subdomain of a domain already managed by Sleakops as a Provider or Environment **in the same account** (e.g. `api.external-domain.com` under `external-domain.com`): +- ✅ Reuses that domain's certificate automatically — no separate SSL validation needed (a parent in a different account doesn't count: the alias then gets its own certificate with manual validation, as in Scenario B) - ✅ Provides ALB name for DNS configuration -- ⚠️ You configure the DNS records yourself +- ⚠️ You still create the CNAME (or A/ALIAS record for a root domain) pointing to the ALB yourself ### Scenario B: Domain doesn't match any hosted zone If `anything.com` is completely external: diff --git a/content/docs/en/domain/setup.mdx b/content/docs/en/domain/setup.mdx index cb7795bd5..f44c283ef 100644 --- a/content/docs/en/domain/setup.mdx +++ b/content/docs/en/domain/setup.mdx @@ -12,7 +12,7 @@ import { FiExternalLink } from "react-icons/fi"; One critical aspect of working with SleakOps is ensuring proper domain delegation. Domain delegation is essential for seamless integration and functionality, as it determines how your domains and subdomains are managed and how they interact with your AWS environment. Depending on your specific needs, there are several scenarios for domain delegation with SleakOps: -#### 1. Navigate to the providers section +#### 1. Delegate the Main Domain This is the simplest option, where the NS record of the main domain is pointed to your AWS Hosted Zone. All subdomains will be handled automatically, ensuring effortless management. @@ -20,10 +20,6 @@ This is the simplest option, where the NS record of the main domain is pointed t If you prefer to keep your principal domain managed by your current DNS provider—perhaps because it hosts core services like email—this option allows you to delegate only the necessary subdomains. You'll need to set the NS records for each subdomain you wish to delegate. -#### 2. No Delegation of Main Domain or Subdomains - -If you prefer to keep your principal domain managed by your current DNS provider—perhaps because it hosts core services like email—this option allows you to delegate only the necessary subdomains. You'll need to set the NS records for each subdomain you wish to delegate. - #### 3. No Delegation of Main Domain or Subdomains In this case, you maintain full control over your domain and subdomains, without delegating them to AWS. To ensure SleakOps functions correctly, you must: @@ -35,9 +31,9 @@ In this case, you maintain full control over your domain and subdomains, without If you want to use a domain other than the principal one or have multiple domains pointing to the same service, you'll need to create an ALIAS: -- If the ALIAS belongs to a domain managed by SleakOps, it will be handled automatically. +- If the ALIAS is a direct subdomain of a domain already managed by SleakOps **in the same account**, it reuses that domain's certificate automatically — you still need to create the CNAME record pointing to the load balancer. If the parent domain belongs to a different account, the alias gets its own certificate with manual validation records. - If not, you'll need to manually create: - - A CNAME record to validate the SSL Certificate.' + - A CNAME record to validate the SSL Certificate. - An additional record for each ALIAS. By understanding and applying the appropriate domain delegation strategy for your environment, you can ensure that SleakOps integrates smoothly with your AWS infrastructure, providing optimal performance and security. @@ -76,7 +72,7 @@ To access it, there are are different ways, based on what you need to do: a. Access the Workload’s list and then, the Web services section. b. Select and Workload and click on the Three Dots button. c. Choose the Detail option - d. Create the Alias if it doesn’t exist by clicking the Associate new Domain and completing the form. + d. Create the Alias if it doesn’t exist by clicking the Associate new Domain and completing the form (the form includes a deploy option, checked by default, that redeploys the service immediately to start serving the new domain — if you uncheck it, the alias is saved without deploying and you'll need to deploy the affected projects yourself for it to take effect). e. Click on the Alias domain to display the detail.Go from repository to a fully deployed application without writing a single config file. AI generates everything for you.
+Go from repository to deployable infrastructure without writing a single config file. AI generates the setup — you review and create each resource with a click.
Learn more diff --git a/content/docs/en/project/access_config.mdx b/content/docs/en/project/access_config.mdx index a2bfadd93..f689b7b05 100644 --- a/content/docs/en/project/access_config.mdx +++ b/content/docs/en/project/access_config.mdx @@ -17,6 +17,10 @@ The Access Configuration allows you to extend your project's permissions by gran 3. Configure external dependencies and extra policies as needed 4. Click **Apply changes** to save your configuration +:::info +Applying changes requires the project to be in **Created** or **Error** state. While the change is applied, the project shows **Updating**. +::: +
diff --git a/content/docs/en/project/build_resources.mdx b/content/docs/en/project/build_resources.mdx
index 38cda0667..b57f87cb5 100644
--- a/content/docs/en/project/build_resources.mdx
+++ b/content/docs/en/project/build_resources.mdx
@@ -22,7 +22,7 @@ The Deploy Build Resources configuration allows you to specify the CPU and memor
Access the Deploy Build Resources settings:
1. Navigate to **Project** → **Settings**
-2. Select **Deploy Build Resources** from the settings menu
+2. Select **Deploy and Build Resources** from the settings menu
3. Configure the resource values according to your project's requirements
4. Click **Save** to apply the changes
@@ -80,7 +80,7 @@ This is a common issue when dealing with:
If you're experiencing build or deployment failures due to resource constraints, you can increase the allocated resources:
1. Navigate to **Project** → **Settings** in the SleakOps interface
-2. Select **Deploy Build Resources** from the settings menu
+2. Select **Deploy and Build Resources** from the settings menu
3. Increase the values for the resource that's causing issues:
- **Build Request CPU**: Increase if builds are slow or CPU-throttled
- **Build Request Memory**: Increase if builds fail with OOMKilled errors
diff --git a/content/docs/en/project/chart/chart_dependencies.mdx b/content/docs/en/project/chart/chart_dependencies.mdx
index 28d662c4d..04190eb87 100644
--- a/content/docs/en/project/chart/chart_dependencies.mdx
+++ b/content/docs/en/project/chart/chart_dependencies.mdx
@@ -33,6 +33,7 @@ To add a new Chart Dependency, click the **Create** button in the Chart Configur
1. **Search and Select**: Use the first two fields to search for the chart name and select your desired version
2. **Configure Values**: Modify the values section below to customize the deployment
3. **Set Tolerations**: **Critical** - Update all `tolerations` fields in the chart values to target your NodePool
+4. **Deploy**: leave **Deploy?** on to deploy the change immediately, or turn it off to save it as a pending change
-- Via the [CLI ](/docs/cli).
\ No newline at end of file
+- Via the [CLI ](/docs/cli).
+
+### Canceling a Deployment
+
+While a Deployment is still queued and hasn't started running, Admins and Editors can cancel it from the Deployments list. If a Deployment fails, click its status to open the log viewer and see the error details.
\ No newline at end of file
diff --git a/content/docs/en/project/deployment/more_on_deployment.mdx b/content/docs/en/project/deployment/more_on_deployment.mdx
index 86947578f..6164b8d6a 100644
--- a/content/docs/en/project/deployment/more_on_deployment.mdx
+++ b/content/docs/en/project/deployment/more_on_deployment.mdx
@@ -35,4 +35,4 @@ As you may already know, if it's not a 'forced' deployment, you'll be presented
- [Workloads](/docs/project/workload) Alias Configuration Changes: A Deployment is forced if any alterations are made to the 'alias' configuration.
- [Dependency](/docs/project/dependency): Always forces a Deployment to synchronize its associated VariableGroup state with the templates of the Helm Chart ensuring that Services operation is not affected.
-- [VariableGroup](/docs/project/vargroup) Deletion: Same case as Dependency deletion.
+- [VariableGroup](/docs/project/vargroup) Deletion: Same case as Dependency deletion — it always redeploys the projects that use it.
diff --git a/content/docs/en/project/deployment/release.mdx b/content/docs/en/project/deployment/release.mdx
index b25a16325..a5ed5ebf0 100644
--- a/content/docs/en/project/deployment/release.mdx
+++ b/content/docs/en/project/deployment/release.mdx
@@ -11,7 +11,7 @@ In Sleakops, a release represents a deployable state of all the Workloads (web s
## Release Creation
-Sleakops administers releases for you. Every time you modify, delete, or add a web service, worker, hook, or cron job, Sleakops gives you the option to publish the changes. Each time you publish those changes, Sleakops creates a new release with auto-incremented versions.
+Sleakops administers releases for you. Every time you add, edit, or delete a web service, worker, hook, or cron job — or edit a chart resource like [chart dependencies](/docs/project/chart/chart_dependencies) or [extra templates](/docs/project/chart/extra_templates) — Sleakops gives you the option to publish the changes. Each time you publish, Sleakops creates a new release with an auto-incremented version: adding or removing a workload bumps the minor version, while any other change bumps the patch version.
### Helm Chart Resources
diff --git a/content/docs/en/project/dockertron.mdx b/content/docs/en/project/dockertron.mdx
index 8cfc196de..ae59b9f8c 100644
--- a/content/docs/en/project/dockertron.mdx
+++ b/content/docs/en/project/dockertron.mdx
@@ -6,13 +6,13 @@ sidebar_position: 2
import Zoom from "react-medium-image-zoom";
import "react-medium-image-zoom/dist/styles.css";
-# Technical Documentation - Dockertron
+# Dockertron
## Executive Summary
**Dockertron** is an automated dockerization system that analyzes your source code and automatically generates the necessary infrastructure to run your application in Docker containers. The system uses artificial intelligence to understand your project structure and create the appropriate configuration files.
-You can find it in SleakOps in the **Projects > Configuration > Dockertron section.**
+Start an execution from the **Dockertron IA** button on the Projects or Environments page, or from the **Configure your project with Dockertron AI** banner on the project creation form.
@@ -39,20 +39,20 @@ Dockertron automates the containerization process of your application following
### 1. Submit the Project
To select an account and be able to work on it, select it from the left pane.
The left icon refers to the Provider that groups the accounts.
+Editors and Viewers only see the accounts they've been granted access to.
diff --git a/content/docs/en/provider/common-errors.mdx b/content/docs/en/provider/common-errors.mdx index a75ac260e..3882aa020 100644 --- a/content/docs/en/provider/common-errors.mdx +++ b/content/docs/en/provider/common-errors.mdx @@ -39,7 +39,17 @@ Before retrying the process, increase that limit. Otherwise, the process will fa />
diff --git a/content/docs/en/user/index.mdx b/content/docs/en/user/index.mdx
index 07c5f3b0c..75c4be5ae 100644
--- a/content/docs/en/user/index.mdx
+++ b/content/docs/en/user/index.mdx
@@ -67,7 +67,7 @@ Sleakops has three fundamental fields of user permissions:
-Only administrators can delete users. To delete a user, access the User List, in the Action column, click on the bin icon. Then confirm the action.
+Only administrators can delete users. To delete a user, access the User List, in the Action column, click on the bin icon. Then confirm the action. An admin cannot delete their own account.
SleakOps automatically handles the complete deletion process across all systems (IAM user, Pritunl VPN server user, and SleakOps console user). No additional manual steps are required outside the SleakOps console.
@@ -83,28 +83,23 @@ Deleted users cannot be recovered. However, deleting a user never removes any re
-For access into the AWS accounts SleakOps initially sets a random password and sends it to the email of the created user. The user can login with that password but it will be obligated to change its password on the first login. For SleakOps platform access we use the password that was set on the User form.
+For access into the AWS accounts SleakOps initially sets a random password and sends it to the email of the created user. The user can login with that password but it will be obligated to change its password on the first login. For SleakOps platform access, the user gets a separate email with a link to set their own password.
After this user creation an AWS User will be created on the 'security' Account, this account is where we control acesses to all the SleakOps AWS accounts. We will also create, depending on the configuration, users on the VPN servers, read how to use them on the corresponding [documentation ](/docs/user/vpn) and on the SleakOps user.
-## Users Without SleakOps Access
+## AWS/VPN-Only Members
-Some users in your organization may not have direct access to the SleakOps platform but still interact with the infrastructure:
+Turning off console access is only available for the Viewer role. It creates a member with no SleakOps login who still gets AWS IAM and/or VPN access provisioned for the accounts you assign — useful for external collaborators, auditors, or teammates who only need infrastructure access, not a console seat. At least one AWS or VPN account is required in this case.
-### External Collaborators
+## Managing Members
-- **Scenario**: Third-party contractors or consultants who need temporary access to specific AWS resources
-- **Access Method**: Direct AWS console access with limited IAM permissions
-- **Management**: Handled through AWS IAM directly, not through SleakOps user management
+Admins can act on any member from the Members list or its detail drawer:
-### Read-Only Observers
+- **Reset AWS Password**: pick the provider and confirm — SleakOps generates a new IAM password and emails it to the member.
+- **Get Pritunl Credentials**: for members without SleakOps console access, who can't fetch their own VPN URI (see the [VPN documentation](/docs/user/vpn)), an admin retrieves it for any account where the member already has a provisioned VPN profile.
-- **Scenario**: Stakeholders who need visibility into infrastructure costs and usage without operational access
-- **Access Method**: AWS Cost Explorer, CloudWatch dashboards, or custom reporting tools
-- **Management**: AWS billing and monitoring permissions only
+Editing a member only lets you change their role and account access; name, email, and console access are fixed at creation.
-### VPN-Only Consumers
-
-- **Scenario**: Users who need to consume workloads and applications within the VPN but don't require infrastructure administration or monitoring capabilities
-- **Access Method**: VPN access only, with limited permissions to access specific applications and services
-- **Management**: VPN user accounts with restricted access to designated workloads and environments
+:::info
+Changing a member's role re-provisions their AWS and VPN access automatically. If the member uses `kubectl`, they need to regenerate their kubeconfig to pick up the new permissions.
+:::
diff --git a/content/docs/en/user/vpn.mdx b/content/docs/en/user/vpn.mdx
index 96d2ddd1e..c2482f45b 100644
--- a/content/docs/en/user/vpn.mdx
+++ b/content/docs/en/user/vpn.mdx
@@ -15,6 +15,10 @@ To handle VPN connections we use Pritunl. You can download the client [here](htt
Once you've created a [Provider ](/docs/provider), go to [SleakOps dashboard](https://console.sleakops.com/) and select the account for which you want to get VPN access. Remember, to do this, you need to have access to the VPN of that account, but the VPN must also be created. We create the VPN of a specific account when the first cluster of that account is created.
+:::info
+This self-service flow requires SleakOps console access. If your account is VPN-only (no console login), ask an admin to retrieve your profile URI from [Members](/docs/user) instead.
+:::
+
-This will prompt you with what is called the URI profile. It has a validation period of 24 hours, and you must load it into the Pritunl client.
+This will prompt you with what is called the URI profile. It is valid for 24 hours — after that, request a new one from the panel. Load it into the Pritunl client, and treat it as a credential: don't share it, since anyone who imports it can connect as you.
diff --git a/content/docs/es/cluster/access-cluster.mdx b/content/docs/es/cluster/access-cluster.mdx
index 6ba4aac14..e0cec2213 100644
--- a/content/docs/es/cluster/access-cluster.mdx
+++ b/content/docs/es/cluster/access-cluster.mdx
@@ -7,6 +7,10 @@ import Zoom from "react-medium-image-zoom";
Para acceder a tu clúster de Kubernetes, debes completar algunos pasos y generar un archivo Kubeconfig para conectarte a un IDE de Kubernetes.
+:::tip
+¿Prefieres no instalar un IDE de Kubernetes? El add-on [Headlamp](/docs/cluster/addons/headlamp) te da una interfaz de Kubernetes desde el navegador, sin necesidad de Kubeconfig ni de instalar Lens; aun así necesitas estar conectado a la VPN para acceder.
+:::
+
## Preguntas Frecuentes
-
-
Haz clic en Eliminar para confirmar y activar la acción en SleakOps.
Del repositorio a una aplicación desplegada sin escribir un solo archivo de configuración. La IA genera todo por vos.
+Del repositorio a infraestructura lista para desplegar sin escribir un solo archivo de configuración. La IA genera la base — vos revisás y creás cada recurso con un clic.
Más información diff --git a/content/docs/es/project/access_config.mdx b/content/docs/es/project/access_config.mdx index 70660d8f9..c7abf7782 100644 --- a/content/docs/es/project/access_config.mdx +++ b/content/docs/es/project/access_config.mdx @@ -17,6 +17,10 @@ La Configuración de Acceso te permite extender los permisos de tu proyecto otor 3. Configura las dependencias externas y políticas adicionales según sea necesario 4. Haz clic en **Aplicar cambios** para guardar tu configuración +:::info +Para aplicar cambios el proyecto debe estar en estado **Created** o **Error**. Mientras se aplica el cambio, el proyecto muestra el estado **Updating**. +::: +
diff --git a/content/docs/es/project/build/index.mdx b/content/docs/es/project/build/index.mdx
deleted file mode 100644
index 8bdb25000..000000000
--- a/content/docs/es/project/build/index.mdx
+++ /dev/null
@@ -1,91 +0,0 @@
----
-sidebar_position: 6
----
-import { FiExternalLink } from "react-icons/fi";
-
-
-# Build
-
-Hemos hablado repetidamente sobre el Build tanto en la [Documentación de Proyectos](/docs/project) como en la [Documentación del Build Inicial](/docs/project). Un build es básicamente una plantilla de un sistema operativo, bibliotecas y otras dependencias del proyecto que despliegas.
-
-### Creación del Build
-
-Para crear un Build solo necesitas cuatro parámetros; solo el campo **Proyecto** es obligatorio, ya que los otros tres, si no se configuran, esperan hasta que este acceso se habilite automáticamente y se eligen por defecto:
-- **Proyecto**: Se refiere a lo que llamamos ProjectEnv. Aquí eliges el ProjectEnv que deseas construir.
-- **Branch**: Te permite elegir cualquier rama del repositorio que hayas elegido como Proyecto. Por defecto, se utiliza el nombre del Entorno.
-- **Commit hash**: También puedes elegir el hash del commit para construir un commit específico y no el último, como lo hacemos por defecto. Por defecto, se utiliza el último commit.
-- **Tag**: Un tag para diferenciar los builds. Por defecto, es 'latest'.
-
-## ¿Por qué necesitamos crear una imagen Docker?
-
-Dado que utilizamos [Helm charts
-- A través del [CLI ](/docs/cli).
\ No newline at end of file
+- A través del [CLI ](/docs/cli).
+
+### Cancelar un Deployment
+
+Mientras un Deployment todavía está en cola y no comenzó a ejecutarse, los Admins y Editors pueden cancelarlo desde la lista de Deployments. Si un Deployment falla, hacé clic en su estado para abrir el visor de logs y ver el detalle del error.
\ No newline at end of file
diff --git a/content/docs/es/project/deployment/more_on_deployment.mdx b/content/docs/es/project/deployment/more_on_deployment.mdx
index 52f2b9608..25b95a8a5 100644
--- a/content/docs/es/project/deployment/more_on_deployment.mdx
+++ b/content/docs/es/project/deployment/more_on_deployment.mdx
@@ -35,4 +35,4 @@ Como ya sabes, si no es un deployment 'forzado', se te presentará una opción (
- Cambios en la configuración del [Workload](/docs/project/workload) Alias: Un Deployment es forzado si se realizan modificaciones en la configuración del 'alias'.
- [Dependency](/docs/project/dependency): Siempre fuerza un Deployment para sincronizar el estado de su VariableGroup asociado con las plantillas del Helm Chart, asegurando que el funcionamiento de los Workloads no se vea afectado.
-- Eliminación de [VariableGroup](/docs/project/vargroup): Igual que la eliminación de Dependency.
\ No newline at end of file
+- Eliminación de un [VariableGroup](/docs/project/vargroup): Mismo caso que la eliminación de una Dependency — siempre redespliega los proyectos que lo usan.
\ No newline at end of file
diff --git a/content/docs/es/project/deployment/release.mdx b/content/docs/es/project/deployment/release.mdx
index 81ec566c9..dbd1d8ff5 100644
--- a/content/docs/es/project/deployment/release.mdx
+++ b/content/docs/es/project/deployment/release.mdx
@@ -11,7 +11,7 @@ En Sleakops, un release representa un estado desplegable de todos los servicios
## Creación de Releases
-Sleakops administra los releases por ti. Cada vez que modificas, eliminas o agregas un servicio, worker, hook o cron job, Sleakops te da la opción de publicar los cambios. Cada vez que publicas esos cambios, Sleakops crea un nuevo release con versiones auto-incrementadas.
+Sleakops administra los releases por ti. Cada vez que agregas, editas o eliminas un servicio web, worker, hook o cron job — o editas un recurso del chart como [chart dependencies](/docs/project/chart/chart_dependencies) o [extra templates](/docs/project/chart/extra_templates) — Sleakops te da la opción de publicar los cambios. Cada vez que publicas, Sleakops crea un nuevo release con una versión auto-incrementada: agregar o eliminar un workload incrementa la versión minor, mientras que cualquier otro cambio incrementa la versión patch.
### Recursos del Helm Chart
diff --git a/content/docs/es/project/dockertron.mdx b/content/docs/es/project/dockertron.mdx
index 673c98fcf..307dc2f36 100644
--- a/content/docs/es/project/dockertron.mdx
+++ b/content/docs/es/project/dockertron.mdx
@@ -6,13 +6,13 @@ sidebar_position: 2
import Zoom from "react-medium-image-zoom";
import "react-medium-image-zoom/dist/styles.css";
-# Dockertron - Generación de Dockerfiles y Docker Compose
+# Dockertron
## Resumen
**Dockertron** es un sistema automatizado de dockerización que analiza su código fuente y genera automáticamente la infraestructura necesaria para ejecutar su aplicación en contenedores Docker. El sistema utiliza inteligencia artificial para comprender la estructura de su proyecto y crear los archivos de configuración apropiados.
-Podes encontrarlo en Sleakops en la sección de **Proyectos>Configuración>Docketron.**
+Inicie una ejecución desde el botón **Dockertron IA** en la página de Proyectos o Entornos, o desde el banner **Configure your project with Dockertron AI** del formulario de creación de proyecto.
@@ -43,16 +43,16 @@ Dockertron automatiza el proceso de containerización de su aplicación siguiend
**
@@ -110,23 +110,23 @@ Puedes monitorear tu projecto accediendo a *Projects*, seleccionando uno **y hac
Para seleccionar una cuenta y poder trabajar en ella, selecciónala desde el panel izquierdo.
El icono de la izquierda se refiere al Provider que agrupa las cuentas.
+Los Editores y Viewers solo ven las cuentas a las que se les otorgó acceso.
diff --git a/content/docs/es/provider/common-errors.mdx b/content/docs/es/provider/common-errors.mdx index 0cec98430..afbdcdd88 100644 --- a/content/docs/es/provider/common-errors.mdx +++ b/content/docs/es/provider/common-errors.mdx @@ -39,7 +39,17 @@ Antes de volver a intentar el proceso, aumenta ese límite. De lo contrario, el /> -### 3. Otros errores +### 3. La creación de la cuenta sigue en proceso en AWS + +A veces AWS necesita algunos minutos más para terminar de configurar una cuenta recién creada antes de que SleakOps pueda usarla. + +Verás un botón *Retry*, deshabilitado temporalmente durante unos minutos. Si los reintentos siguen fallando, contacta al soporte de AWS indicando los ID de cuenta que se muestran en pantalla. + +### 4. Una de tus cuentas de AWS está suspendida, en proceso de cierre o cerrada + +Contacta a AWS Support para resolver el estado de la cuenta y luego vuelve a intentar la conexión. + +### 5. Otros errores Pueden surgir otros problemas que generalmente se resuelven ejecutando nuevamente la conexión con AWS. diff --git a/content/docs/es/provider/deleting-a-provider.mdx b/content/docs/es/provider/deleting-a-provider.mdx index 1904794a7..27ffffcd5 100644 --- a/content/docs/es/provider/deleting-a-provider.mdx +++ b/content/docs/es/provider/deleting-a-provider.mdx @@ -7,13 +7,17 @@ import Zoom from "react-medium-image-zoom"; # Eliminar un Provider -- Esta función te permite eliminar un Provider y todo lo que fue creado bajo él. -- Solo los Providers *creados exitosamente* y aquellos con *error* pueden ser eliminados. Si no ves la opción, probablemente el Provider está en otro estado. +- Esta función te permite eliminar un Provider y todo lo que fue creado bajo él. Solo los Admins pueden hacerlo. +- Solo los Providers en estado *Initial*, *creados exitosamente* o con *error* pueden ser eliminados — no mientras hay una tarea de aprovisionamiento, actualización o eliminación en curso. Eliminar un Provider que sigue en *Initial* (antes de terminar la conexión con AWS) es inmediato, ya que todavía no se creó nada en AWS. :::warning La *Organización* creada y sus cuentas (gestión, desarrollo, producción y seguridad) no se eliminarán automáticamente. Aunque mantener estas cuentas bajo tu Cuenta Root de AWS no genera costos, **recomendamos eliminarlas** manualmente. ::: +:::note +Si una dependencia (por ejemplo, una base de datos) tiene la protección contra eliminación habilitada, la solicitud de eliminación fallará hasta que la deshabilites. +::: + ## Cómo eliminar un Provider ### 1. Selecciona el Provider a eliminar diff --git a/content/docs/es/provider/index.mdx b/content/docs/es/provider/index.mdx index 4c9127c9b..1726319cb 100644 --- a/content/docs/es/provider/index.mdx +++ b/content/docs/es/provider/index.mdx @@ -75,7 +75,7 @@ Para comenzar la instalación de tu aplicación, necesitamos conectarnos a tu Cu Crear una Unidad Organizativa no genera ningún costo en tu cuenta de AWS 😃 ::: -Una vez establecida la conexión y creado el rol, SleakOps iniciará automáticamente la creación de la Unidad Organizativa. +Una vez establecida la conexión y creado el rol, SleakOps iniciará automáticamente la creación de la Unidad Organizativa. Si tu cuenta root ya pertenece a una Organización de AWS, SleakOps la reutilizará en lugar de crear una nueva. Este proceso tomará unos minutos. diff --git a/content/docs/es/subscribe-using-aws.mdx b/content/docs/es/subscribe-using-aws.mdx index fbeddd6a0..557b3d575 100644 --- a/content/docs/es/subscribe-using-aws.mdx +++ b/content/docs/es/subscribe-using-aws.mdx @@ -23,9 +23,9 @@ Bienvenido a nuestra guía sobre cómo suscribirse a SleakOps usando AWS. Este t Inicia sesión en SleakOps usando una cuenta **Admin**. -### 2. Ir a Settings > Subscription +### 2. Ir a Settings > Billing > Subscription -Desde el menú izquierdo, accedé a la opción **Settings** en la parte inferior, y luego seleccioná la opción **Subscription**. +Desde el menú izquierdo, accedé a la opción **Settings** en la parte inferior, y luego seleccioná **Subscription**, dentro del grupo **Billing** (solo admin).
-This will prompt a new AWS tab to switch the role from your 'security' Account into the account you've selected, you'll leave the 'security account' and enter the selected one.
+Esto abrirá una nueva pestaña de AWS para cambiar de rol desde tu cuenta 'security' hacia la cuenta seleccionada: saldrás de la cuenta 'security' e ingresarás a la elegida.