Skip to content

chore: add more details on efs and ebs usage#81

Closed
karim090 wants to merge 2 commits intodevelopfrom
extra/ebs-efs-usage
Closed

chore: add more details on efs and ebs usage#81
karim090 wants to merge 2 commits intodevelopfrom
extra/ebs-efs-usage

Conversation

@karim090
Copy link
Copy Markdown
Contributor

@karim090 karim090 commented Nov 15, 2024

Summary by CodeRabbit

  • Nuevas características
    • Se agregó una nueva sección en la documentación de AWS EBS sobre cómo usar volúmenes EBS en gráficos personalizados.
    • Se añadió una nueva sección en la documentación de AWS EFS con instrucciones sobre el uso de volúmenes EFS en gráficos personalizados.
  • Documentación
    • Instrucciones para pasar el nombre de 'StorageClass' al usar volúmenes EBS y EFS.
    • Comando para verificar las StorageClasses actuales en el entorno de Kubernetes.

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Nov 15, 2024

Walkthrough

Se han realizado cambios en la documentación de AWS EBS y EFS en los archivos docs/cluster/addons/ebs.mdx y docs/cluster/addons/efs.mdx. Se han añadido nuevas secciones que explican cómo usar volúmenes EBS y EFS en gráficos personalizados, incluyendo instrucciones sobre cómo pasar el nombre de 'StorageClass'. También se proporciona un comando para verificar las StorageClasses disponibles en el entorno de Kubernetes. La estructura general de los documentos se mantiene intacta.

Changes

Archivo Resumen de cambios
docs/cluster/addons/ebs.mdx - Nueva sección: <details> con el resumen ¿Cómo uso volúmenes EBS en mis propios gráficos?
- Nueva instrucción sobre el uso de volúmenes EBS y cómo verificar las StorageClasses actuales.
docs/cluster/addons/efs.mdx - Nueva sección: ¿Cómo uso volúmenes EFS en mis propios gráficos?
- Nueva instrucción sobre el uso de volúmenes EFS y selección de 'StorageClass'.
- Comando añadido: kubectl get storageclass --all-namespaces.

Possibly related PRs

Suggested reviewers

  • sourcery-ai
  • lucaiz
  • agustinoli

🎉 En la nube brillan las guías,
EBS y EFS, ¡qué maravillas!
Con comandos y secciones nuevas,
La documentación se renueva.
¡A usar volúmenes con alegría!
En Kubernetes, ¡todo es armonía! 🌟


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between b74d0ad and 108f95c.

📒 Files selected for processing (2)
  • docs/cluster/addons/ebs.mdx (1 hunks)
  • docs/cluster/addons/efs.mdx (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (2)
  • docs/cluster/addons/ebs.mdx
  • docs/cluster/addons/efs.mdx

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Copy Markdown

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 3

🧹 Outside diff range and nitpick comments (3)
docs/cluster/addons/ebs.mdx (1)

43-43: ¡Vamos a darle más chicha a esta documentación!

¡Eh, compañero! La explicación sobre el StorageClass está más flaca que un fideo. Deberíamos mostrar un ejemplo completo de cómo se usa en los values.yaml.

Agrega un ejemplo así:

To use EBS Volumes you must pass to the chart values the 'StorageClass' name 'gp2'.
+
+Example in values.yaml:
+```yaml
+persistence:
+  enabled: true
+  storageClass: "gp2"
+  size: 10Gi
+```
docs/cluster/addons/efs.mdx (2)

47-57: ¡Metele más chicha a la documentación, papá!

La sección está buena pero le falta más información jugosa:

  • Agregar un ejemplo de cómo configurar el StorageClass en los values.yaml
  • Explicar la diferencia entre las políticas 'delete' y 'retain'
  • Mencionar las limitaciones o consideraciones importantes al usar EFS

¿Querés que te ayude a expandir esta sección con más detalles? ¡Nomás avisá y nos ponemos las pilas!


55-57: ¡Dale formato al comando, maestro!

El bloque de código necesita un identificador de lenguaje para mejor resaltado de sintaxis.

Cambialo así:

-```
+```bash
kubectl get storageclass --all-namespaces

</blockquote></details>

</blockquote></details>

<details>
<summary>📜 Review details</summary>

**Configuration used: CodeRabbit UI**
**Review profile: CHILL**

<details>
<summary>📥 Commits</summary>

Reviewing files that changed from the base of the PR and between 9dd6fd1e96f67d06a95c04ed3805bab12c2d489b and b74d0addfd46a9ae78c6e28d82946bb4fcf657c0.

</details>

<details>
<summary>📒 Files selected for processing (2)</summary>

* `docs/cluster/addons/ebs.mdx` (1 hunks)
* `docs/cluster/addons/efs.mdx` (1 hunks)

</details>

</details>

<!-- This is an auto-generated comment by CodeRabbit for review status -->

Comment on lines +47 to +49
```
kubectl get storageclass --all-namespaces
```
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

¡Dale más contexto al comando, maestro!

El comando está más solo que un árbitro en una final. ¡Vamos a explicar qué significa la salida y qué debe buscar el usuario!

Agrega esta información:

kubectl get storageclass --all-namespaces

+
+This command will show all available StorageClasses. Look for the `gp2` StorageClass, which should be marked as `(default)`. Example output:
+
+```
+NAME            PROVISIONER             RECLAIMPOLICY   VOLUMEBINDINGMODE      ALLOWVOLUMEEXPANSION   AGE
+gp2 (default)   kubernetes.io/aws-ebs   Delete          WaitForFirstConsumer   true                   1d
+```
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
```
kubectl get storageclass --all-namespaces
```
```
kubectl get storageclass --all-namespaces
```
This command will show all available StorageClasses. Look for the `gp2` StorageClass, which should be marked as `(default)`. Example output:
```
NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE
gp2 (default) kubernetes.io/aws-ebs Delete WaitForFirstConsumer true 1d
```

Comment thread docs/cluster/addons/ebs.mdx Outdated
Comment on lines +44 to +46
<summary>
You can check your current StorageClasses
</summary>
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue

¡Ojo! Hay un summary perdido dentro del details

¡A las piñas con ese summary que está mal colocado! 💪 Necesitamos arreglar la estructura del MDX para que quede más limpio que un peso recién acuñado.

Aplica este cambio para dejarlo más ordenado:

To use EBS Volumes you must pass to the chart values the 'StorageClass' name 'gp2'.
-<summary>
-You can check your current StorageClasses 
-</summary>

You can check your current StorageClasses with:
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
<summary>
You can check your current StorageClasses
</summary>
You can check your current StorageClasses with:

Comment thread docs/cluster/addons/efs.mdx Outdated
Comment on lines +51 to +54
To use EFS Volumes you must pass to the chart values the 'StorageClass' name 'efs-sc-delete' or 'efs-sc-retain' depending of which [retain policy <FiExternalLink/>](https://kubernetes.io/docs/concepts/storage/storage-classes/) is needed.
<summary>
You can check your current StorageClasses
</summary>
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue

¡Che, tenemos un problemita con el formato!

¡A las piñas con el MDX! Hay un error en la estructura:

  • Tenés un <summary> anidado dentro de otro <summary>
  • Falta el cierre del primer </summary>

Dale con este cambio:

To use EFS Volumes you must pass to the chart values the 'StorageClass' name 'efs-sc-delete' or 'efs-sc-retain' depending of which [retain policy <FiExternalLink/>](https://kubernetes.io/docs/concepts/storage/storage-classes/) is needed.
-<summary>
You can check your current StorageClasses 
-</summary>

To check your current StorageClasses, run:
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
To use EFS Volumes you must pass to the chart values the 'StorageClass' name 'efs-sc-delete' or 'efs-sc-retain' depending of which [retain policy <FiExternalLink/>](https://kubernetes.io/docs/concepts/storage/storage-classes/) is needed.
<summary>
You can check your current StorageClasses
</summary>
To use EFS Volumes you must pass to the chart values the 'StorageClass' name 'efs-sc-delete' or 'efs-sc-retain' depending of which [retain policy <FiExternalLink/>](https://kubernetes.io/docs/concepts/storage/storage-classes/) is needed.
To check your current StorageClasses, run:

<summary>
**How do I use ebs volumes on my own charts?**
</summary>
To use EBS Volumes you must pass to the chart values the 'StorageClass' name 'gp2'.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Aca por las dudas el mejor para usar es 'ebs-csi-default-sc' que es de gp3 y se instala con el EBS CSI Driver. O sea tambien se puede usar gp2 pero no tendria sentido hacerlo

@mjroson
Copy link
Copy Markdown
Member

mjroson commented Nov 21, 2024

cierro esta PR ya esta dentro de #80

@mjroson mjroson closed this Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants