+
+
+ />
+
+
+
-
-
-### 4. Generate your AWS Keys and generate the kubeconfig file
-
-- Login into AWS with your username.
-- Then, go to [AWS Access Key Wizard](https://us-east-1.console.aws.amazon.com/iam/home#/security_credentials/access-key-wizard) to generate the keys on AWS.
-- Paste the keys in the form and generate the kubeconfig file.
-- Copy the output.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- On the left pane, you will see a selector with the account names, select the one you'll use based on how you decide to manage your clusters and environments.
-We suggest to move forward with a Multiple Schema configuration, that aligns with the best practices. To follow this schema select the development account to create the cluster for your staging environments, and the production account for the production cluster.
-Check [Designing your Infra: Single Schema Vs. Multi Schema](/docs/provider/schemas) for more information.
-
-
-
-
-
-
- Once you have selected your node pool, youβll find the access to update and delete them.
-*Each node pool is displayed with CPU and Memory bars that show you how much capacity is left. The full bar represents the total capacity of the node pool, while the colored portion indicates the combined capacity used by all associated projects/workloads.*
-
-
- Click on Delete to confirm and trigger the action on SleakOps.
-
-
-
-
-### Turning On cluster
-
-To turn on a cluster, click on the *Play* button and confirm the action.
-
-This action is available for clusters in *Scheduled Shutdown* and *Off* status
-
-
-
-:::info
-The cron actions that turn the cluster ON or OFF based on the scheduled time will still run even if you have manually turned it ON or OFF.
-:::
\ No newline at end of file
diff --git a/docs/connect_to_git.mdx b/docs/connect_to_git.mdx
deleted file mode 100644
index cea00d83e..000000000
--- a/docs/connect_to_git.mdx
+++ /dev/null
@@ -1,232 +0,0 @@
----
-sidebar_label: Connect to Git
-sidebar_position: 8
----
-
-import Zoom from "react-medium-image-zoom";
-import "react-medium-image-zoom/dist/styles.css";
-import { FiExternalLink } from "react-icons/fi";
-
-# Connect your Git Account
-
-To leverage the full power of SleakOps, you'll need to connect your Git account to our platform. This connection allows SleakOps to access your repositories, enabling seamless integration, automated deployments, and efficient management of your codebases
-
-SleakOps supports integration with the following Git providers:
-- Github
-- GitLab (including self-hosted instances)
-- Bitbucket
-
-## FAQs
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-- A set of worker machines, called nodes, that run containerized applications. -
- Getting Started -- Pieces of underlying infrastructure your apps need to run in the cloud, such - as relational databases, storage services or caches. -
- Getting Started -- An abstract way to expose an application running on a set of Pods as a - network service. -
- Getting Started -
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-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.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-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.
-
-
-
-
-
-
-
-
-
-
-
-
-```plain
-name: Deploy
-
-on:
- push:
- branches:
- - main
-jobs:
- build:
- runs-on: ubuntu-latest
- steps:
- - name: Checkout repository
- uses: actions/checkout@v2
- - name: Install SleakOps CLI
- run: pip install sleakops
- - name: Run SleakOps build
- env:
- SLEAKOPS_KEY: ${{ secrets.SLEAKOPS_KEY }}
- run: sleakops build -p core -b main -w
- deploy:
- needs: [build]
- runs-on: ubuntu-latest
- steps:
- - name: Checkout repository
- uses: actions/checkout@v2
- - name: Install SleakOps CLI
- run: pip install sleakops
- - name: Run SleakOps deploy
- env:
- SLEAKOPS_KEY: ${{ secrets.SLEAKOPS_KEY }}
- run: sleakops deploy -p core -e main -w
-```
-
-
-
-
-```plain
-image: python:3.9
-
-stages:
- - build
- - deploy
-
-build:
- stage: build
- script:
- - apt-get update -qy
- - apt-get install -y python3-pip
- - pip3 install sleakops
- - sleakops build -p core -b main -w
- rules:
- - if: '$CI_COMMIT_BRANCH == main'
-
-deploy:
- stage: deploy
- needs:
- - build
- script:
- - apt-get update -qy
- - apt-get install -y python3-pip
- - pip3 install sleakops
- - sleakops deploy -p core -e prod -w
- rules:
- - if: '$CI_COMMIT_BRANCH == main'
-```
-
-
-
-
-```plain
-image: python:3.9
-
-pipelines:
- branches:
- main:
- - step:
- name: Deploy
- script:
- - apt-get update -qy
- - apt-get install -y python3-pip
- - pip3 install sleakops
- - sleakops build -p core -b main -w
- - sleakops deploy -p core -e main -w
-```
-
-
-
-
-
-### 4. Genera tus Claves de AWS y crea el archivo kubeconfig
-
-- Inicia sesiΓ³n en AWS con tu usuario.
-- Luego, dirΓgete al [Asistente de Claves de Acceso de AWS](https://us-east-1.console.aws.amazon.com/iam/home#/security_credentials/access-key-wizard) para generar las claves en AWS.
-- Pega las claves en el formulario y genera el archivo kubeconfig.
-- Copia el resultado.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- En el panel izquierdo, verΓ‘s un selector con los nombres de las cuentas. Selecciona la que utilizarΓ‘s segΓΊn cΓ³mo decidas gestionar tus clΓΊsteres y [entornos](/docs/environment).
-Sugerimos seguir una configuraciΓ³n de Esquema MΓΊltiple, que se alinea con las mejores prΓ‘cticas. Para seguir este esquema, selecciona la cuenta de desarrollo para crear el clΓΊster para tus entornos de pruebas y la cuenta de producciΓ³n para el clΓΊster de producciΓ³n.
-Consulta [DiseΓ±ando tu Infraestructura: Esquema Simple vs. Esquema MΓΊltiple](/docs/provider/schemas) para mΓ‘s informaciΓ³n.
-
-
-
-
-
-
- Una vez que hayas seleccionado tu Node Pool, encontrarΓ‘s las opciones para actualizar y eliminarlo.
-*Cada Node Pool se muestra con barras de CPU y Memoria que indican cuΓ‘nta capacidad queda disponible. La barra completa representa la capacidad total del Node Pool, mientras que la porciΓ³n coloreada indica la capacidad combinada utilizada por todos los proyectos/workloads asociados.*
-
-
- Haz clic en Eliminar para confirmar y activar la acciΓ³n en SleakOps.
-
-
-
-
-### Encender el cluster
-
-Para encender un cluster, haz clic en el botΓ³n *Play* y confirma la acciΓ³n.
-
-Esta acciΓ³n estΓ‘ disponible para clusters con estado *Apagado Programado* o *Apagado*.
-
-
-
-:::info
-Las acciones cron que encienden o apagan el cluster segΓΊn el horario programado seguirΓ‘n ejecutΓ‘ndose, incluso si lo has encendido o apagado manualmente.
-:::
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/connect_to_git.mdx b/i18n/es/docusaurus-plugin-content-docs/current/connect_to_git.mdx
deleted file mode 100644
index 7f0520262..000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/connect_to_git.mdx
+++ /dev/null
@@ -1,235 +0,0 @@
----
-sidebar_label: Conectar a Git
-sidebar_position: 8
----
-
-
-
-import Zoom from "react-medium-image-zoom";
-import "react-medium-image-zoom/dist/styles.css";
-import { FiExternalLink } from "react-icons/fi";
-
-# Conectar tu Cuenta Git
-
-Para aprovechar todo el potencial de SleakOps, necesitarΓ‘s conectar tu cuenta Git a nuestra plataforma. Esta conexiΓ³n permite a SleakOps acceder a tus repositorios, habilitando una integraciΓ³n perfecta, despliegues automatizados y una gestiΓ³n eficiente de tus bases de cΓ³digo.
-
-SleakOps soporta integraciΓ³n con los siguientes proveedores Git:
-- Github
-- GitLab (incluidas instancias autohospedadas)
-- Bitbucket
-
-## Preguntas Frecuentes
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-Un conjunto de mΓ‘quinas de trabajo, llamadas nodos, que ejecutan aplicaciones en contenedores.
- Comienza aquΓ -Una abstracciΓ³n que nos permite aislar los diferentes recursos.
- Comienza aquΓ -Representa una base de cΓ³digo y es gestionado por un repositorio git.
- Comienza aquΓ -Infraestructura subyacente que tus aplicaciones necesitan para funcionar en la nube, como bases de datos, servicios de almacenamiento o caches.
- Comienza aquΓ -Una manera abstracta de exponer una aplicaciΓ³n en ejecuciΓ³n en un conjunto de Pods como un servicio de red.
- Comienza aquΓ -Un diccionario que proporciona configuraciΓ³n para los servicios.
- Comienza aquΓ -
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-**
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-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.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-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.
-
-
-
-
-
-
-
-
-
-
-
+
+
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 
- 
- 
- 
- 
- 
- 
- 
- 
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-