forked from meshery/meshery
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request meshery#4651 from shubham-tyagi/shubham-tyagi/feat…
…ure-update-spanish-home-and-pages Shubham tyagi/feature update spanish home and pages
- Loading branch information
Showing
42 changed files
with
3,947 additions
and
1,246 deletions.
There are no files selected for viewing
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,30 +1,30 @@ | ||
| --- | ||
| layout: default | ||
| title: Broker | ||
| permalink: concepts/architecture/broker | ||
| type: concepts | ||
| redirect_from: architecture/broker | ||
| abstract: "Meshery broker component fascilitates data streaming between kubernetes cluster components and outside world." | ||
| language: en | ||
| list: include | ||
| --- | ||
|
|
||
| Broker is a custom Kubernetes controller that provides data streaming across independent components of Meshery whether those components are running inside or outside of the Kubernetes cluster. | ||
|
|
||
| ### Broker FAQs | ||
|
|
||
| #### How many Brokers can run? | ||
| It is recommended to run one broker instance for each kubernetes cluster, However the instance itself can be scaled up based on the incoming data volume in each of the cluster. The scaling is independent of the number of instances running. | ||
|
|
||
| #### What does an HA configuration look like? | ||
| We leverage on the kubernetes functionality in terms of the High-Availability behaviour. Meaning, the broker instance gets instantiated/restarted on its own when an issue occurs. In part, Meshery-Operator is also resposible for keeping the broker functional. | ||
|
|
||
| #### What stateful characteristics does the Broker have? | ||
| All the messages that are published to the broker is persisted in-memory within the broker instance until it get consumed. Persistent-volume/Disk-space is not currently being used by the Broker. | ||
|
|
||
| #### How do I know if the Broker is working? How do I troubleshoot the Broker? | ||
| The Broker instance is deployed inside the kubernetes cluster as a `Statefulset`. In the case where the broker doesnt seem to work, here are a few steps to troubleshoot the instance: | ||
|
|
||
| - Make sure the pods corresponding to the `Statefulset` is up and running. | ||
| - Make sure the kubernetes cluster has support for kubernetes `Service` type `LoadBalancer` or `NodePort`. | ||
| - Ensure connectivity between the Meshery-Server and the Broker service endpoint. | ||
| --- | ||
| layout: default | ||
| title: Broker | ||
| permalink: concepts/architecture/broker | ||
| type: concepts | ||
| redirect_from: architecture/broker | ||
| abstract: "Meshery broker component fascilitates data streaming between kubernetes cluster components and outside world." | ||
| language: en | ||
| list: include | ||
| --- | ||
|
|
||
| Broker is a custom Kubernetes controller that provides data streaming across independent components of Meshery whether those components are running inside or outside of the Kubernetes cluster. | ||
|
|
||
| ### Broker FAQs | ||
|
|
||
| #### How many Brokers can run? | ||
| It is recommended to run one broker instance for each kubernetes cluster, However the instance itself can be scaled up based on the incoming data volume in each of the cluster. The scaling is independent of the number of instances running. | ||
|
|
||
| #### What does an HA configuration look like? | ||
| We leverage on the kubernetes functionality in terms of the High-Availability behaviour. Meaning, the broker instance gets instantiated/restarted on its own when an issue occurs. In part, Meshery-Operator is also resposible for keeping the broker functional. | ||
|
|
||
| #### What stateful characteristics does the Broker have? | ||
| All the messages that are published to the broker is persisted in-memory within the broker instance until it get consumed. Persistent-volume/Disk-space is not currently being used by the Broker. | ||
|
|
||
| #### How do I know if the Broker is working? How do I troubleshoot the Broker? | ||
| The Broker instance is deployed inside the kubernetes cluster as a `Statefulset`. In the case where the broker doesnt seem to work, here are a few steps to troubleshoot the instance: | ||
|
|
||
| - Make sure the pods corresponding to the `Statefulset` is up and running. | ||
| - Make sure the kubernetes cluster has support for kubernetes `Service` type `LoadBalancer` or `NodePort`. | ||
| - Ensure connectivity between the Meshery-Server and the Broker service endpoint. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,24 @@ | ||
| --- | ||
| layout: page | ||
| title: 404 | ||
| permalink: es/404.html | ||
| language: es | ||
| excluded_in_search: true | ||
| display-title: "false" | ||
| --- | ||
|
|
||
| <div> | ||
| <h1 id="funny-message" style="font-weight:bold;margin-bottom:1.5em;" class="text-center noTOC"></h1> | ||
| <h3 style="font-style:italic;" class="text-center noTOC">Las cosas tienden a enREDarse por aquí...</h3> | ||
| <div style="text-align:center;" class="alert-info alert">Por favor <a href="https://github.com/layer5io/meshery/issues/new?assignees=&labels=docs&template=documentation.md&title=Docs:" target="_blank">reportar este issue</a> (¡Gracias!) y regresar a la <a href="{{ site.url }}">Documentaión de Meshery </a>.</div> | ||
| </div> | ||
| <script type="text/javascript"> | ||
| var messages = [ | ||
| "Oh, no. Por favor perdone nuestro sitio enREDado.", | ||
| "Oops. Por favor disculpe el enREDo.", | ||
| "Parece que esta página no existe. ¡Qué enREDo!", | ||
| "Por favor disculpe el enREDo." | ||
| ]; | ||
| var message = messages[Math.floor(Math.random()*messages.length)]; | ||
| document.getElementById("funny-message").innerHTML = message; | ||
| </script> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,21 @@ | ||
| --- | ||
| layout: page | ||
| title: Artículos | ||
| permalink: es/archive/ | ||
| language: es | ||
| excluded_in_search: true | ||
| --- | ||
|
|
||
| # Archivo de Noticias | ||
|
|
||
| {% for post in site.posts %}{% capture this_year %}{{ post.date | date: "%Y" }}{% endcapture %}{% capture next_year %}{{ post.previous.date | date: "%Y" }}{% endcapture %} | ||
|
|
||
| {% if forloop.first %}<h2 class="c-archives__year" id="{{ this_year }}-ref">{{this_year}}</h2> | ||
|
|
||
| <ul class="c-archives__list">{% endif %} | ||
| <li class="c-archives__item"> | ||
| {{ post.date | date: "%b %-d, %Y" }}: <a href="{{ post.url | prepend: site.baseurl }}">{{ post.title }}</a> | ||
| </li>{% if forloop.last %}</ul>{% else %}{% if this_year != next_year %} | ||
| </ul> | ||
| <h2 class="c-archives__year" id="{{ next_year }}-ref">{{next_year}}</h2> | ||
| <ul class="c-archives__list">{% endif %}{% endif %}{% endfor %} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,30 +1,31 @@ | ||
| --- | ||
| layout: default | ||
| title: Broker | ||
| permalink: es/concepts/architecture/broker | ||
| permalink: /es/concepts/architecture/broker | ||
| type: concepts | ||
| redirect_from: es/architecture/broker | ||
| abstract: "El componente Meshery broker facilita la transmisión de datos entre los componentes del clúster de Kubernetes y el mundo exterior" | ||
| redirect_from: architecture/broker | ||
| abstract: "El componente broker de Meshery facilita la transmisión de datos entre los componentes del clúster de Kubernetes y el mundo exterior." | ||
| language: es | ||
| list: include | ||
| --- | ||
|
|
||
| El Broker es un controlador de Kubernetes personalizado que provee transmisión de datos a través de componentes independientes de Meshery ya sea que estos componentes estén ejecutándose dentro o fuera del clúster de Kubernetes. | ||
| Broker es un controlador personalizado Kubernetes que provee transmisión de datos a través de componentes independientes de Meshery, ya sea que esos componentes se ejecuten dentro o fuera del clúster de Kubernetes. | ||
|
|
||
| ### Preguntas más Frecuentes del Broker | ||
| ### Preguntas Frequentes del Broker | ||
|
|
||
| #### ¿Cuántos Brokers pueden ejecutarse? | ||
| Se recomienda ejecutar una instancia del Broker para cada clúster de Kubernetes. Sin embargo, la instancia en sí puede ser escalado de acuerdo al volumen de datos entrantes en cada clúster. El escalamiento es independiente de la cantidad de instancias que se ejecutan. | ||
| Se recomienda ejecutar una instancia de agente para cada clúster de kubernetes. Sin embargo, la instancia en sí se puede escalar en función del volumen de datos entrantes en cada uno de los clústeres. El escalado es independiente del número de instancias en ejecución. | ||
|
|
||
| #### ¿Cómo se ve una configuración de Alta Disponibilidad? | ||
| Aprovechamos la funcionalidad de Kubernetes en términos del comportamiento de Alta Disponibilidad. Lo que significa que la instancia del Broker se instancía/reinicia por sí misma cuando se produce un problema. En parte, Meshery Operator es también responsable de mantener al Broker funcional. | ||
| #### ¿Cómo se ve una configuración HA? | ||
| Aprovechamos la funcionalidad de kubernetes en términos del comportamiento de alta disponibilidad(High Avaliavility - HA). Es decir, la instancia del agente se crea una instancia / se reinicia por sí sola cuando ocurre un problema. En parte, Meshery-Operator también es responsable de mantener al corredor en funcionamiento. | ||
|
|
||
| #### ¿Qué características de estado tiene el Broker? | ||
| Todos los mensajes que se publican en el Broker se persisten en memoria dentro de la instancia del Broker hasta que se consuma. El Volumen de persistencia/Espacio del disco no está siendo utilizado actualmente por el Broker. | ||
| #### ¿Qué caracteristicas con estado tiene el Broker? | ||
| Todos los mensajes que se publican en el intermediario se conservan en la memoria dentro de la instancia del intermediario hasta que se consumen. El Broker no está utilizando actualmente el volumen persistente / espacio en disco. | ||
|
|
||
| #### ¿Cómo puedo saber si el Broker está funcionando?, ¿cómo puedo solucionar problemas del Broker? | ||
| La instancia del Broker es desplegada dentro del clúster de Kubernetes como un `Statefulset`. En el caso de que el Broker parezca que no funciona, aquí están algunos pasos para solucionar problemas de la instancia: | ||
| #### ¿Cómo saber si el Broker está funcionando? ¿Cómo solucionar problemas con el Broker? | ||
| La instancia de Broker se implementa dentro del clúster de kubernetes como un "Statefulset". En el caso de que el agente no parezca funcionar, aquí hay algunos pasos para solucionar el problema de la instancia: | ||
|
|
||
| - Asegúrese de que los pods correspondientes al `Statefulset` estén en funcionamiento. | ||
| - Asegúrese de que el clúster de kubernetes sea compatible con el tipo de `Servicio` de kubernetes` LoadBalancer` o `NodePort`. | ||
| - Asegure la conectividad entre Meshery-Server y el punto final del servicio Broker. | ||
|
|
||
| - Asegúrese de que los pods correspondientes al `Statefulset` se encuentren en funcionamiento. | ||
| - Asegúrese de que el clúster de Kubernetes tiene soporte para Kubernetes `Service` tipo `LoadBalancer` o `NodePort`. | ||
| - Asegurar la conectividad entre el Meshery Server y el endpoint del servicio del Broker. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
24 changes: 24 additions & 0 deletions
24
docs/pages/es/concepts/architecture/service-meshes/index.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,24 @@ | ||
| --- | ||
| layout: default | ||
| title: Malla de Servicios | ||
| permalink: es/service-meshes | ||
| type: service-mesh | ||
| list: exclude | ||
| language: es | ||
| # list: exclude | ||
| --- | ||
|
|
||
| Como administrador de múltiples mallas, Meshery ofrece soporte para más adaptadores que cualquier otro proyecto o producto en el mundo. | ||
|
|
||
| ## Soporte para mallas de servicio | ||
|
|
||
| | Service Mesh | Versión de Service Mesh | | ||
| | :----------- | :---------------------: | | ||
|
|
||
| {% for adapter in site.adapters -%} | ||
| {% if adapter.port -%} | ||
| | <img src="{{ adapter.image }}" style="width:20px" /> [{{ adapter.name }}]({{ site.baseurl }}{{ adapter.url }}) | {{ adapter.version }} | | ||
| {% endif -%} | ||
| {% endfor %} | ||
|
|
||
| Meshery admite las siguientes mallas de servicio. Utiliza tanto API de abstracción como adaptadores específicos de malla de servicio para interactuar con las mallas de servicio y administrarlas. Revise la lista completa de [adaptadores]({{ site.baseurl }}/es/architecture/adapters) Meshery . |
Oops, something went wrong.