From 7f281638c891f6ba1d21a30546c79e74d2efa65e Mon Sep 17 00:00:00 2001 From: JOSE ALONSO LOPEZ ROMO Date: Sun, 3 Oct 2021 13:42:48 -0700 Subject: [PATCH 01/18] updating master Signed-off-by: JOSE ALONSO LOPEZ ROMO --- docs/pages/concepts/architecture/broker.md | 60 +- docs/pages/es/404.md | 27 + docs/pages/es/archive.md | 21 + .../es/concepts/architecture/architecture.md | 59 + docs/pages/es/concepts/architecture/broker.md | 30 + .../es/concepts/architecture/database.md | 28 + .../es/concepts/architecture/meshsync.md | 35 + .../es/concepts/architecture/operator.md | 57 + .../architecture/service-meshes/adapters.md | 45 + .../architecture/service-meshes/index.md | 25 + docs/pages/es/concepts/index.md | 28 + docs/pages/es/extensibility/adapters.md | 84 + docs/pages/es/extensibility/api.md | 36 + docs/pages/es/extensibility/extensibility.md | 38 + .../pages/es/extensibility/load-generators.md | 29 + docs/pages/es/extensibility/providers.md | 196 +++ docs/pages/es/functionality/index.md | 6 +- docs/pages/es/functionality/management.md | 7 +- docs/pages/es/functionality/performance.md | 4 +- .../pages/es/functionality/smi-conformance.md | 7 +- docs/pages/es/getting-started/news.md | 30 + docs/pages/es/getting-started/overview.md | 88 + docs/pages/es/guides/index.md | 43 + .../interpreting-performance-test-results.md | 26 + docs/pages/es/guides/meshery-metrics.md | 188 ++ .../es/guides/multiple-of-the-same-adapter.md | 29 + docs/pages/es/guides/sample-apps.md | 79 + docs/pages/es/guides/upgrade.md | 132 ++ .../es/guides/working-with-mesheryctl.md | 216 +++ docs/pages/es/index.md | 167 +- docs/pages/es/installation/aks.md | 5 +- docs/pages/es/installation/docker.md | 5 +- docs/pages/es/installation/eks.md | 3 + docs/pages/es/installation/gke.md | 3 + docs/pages/es/installation/index.md | 7 +- docs/pages/es/installation/kinD.md | 3 + docs/pages/es/installation/kubernetes.md | 3 + docs/pages/es/installation/minikube.md | 3 + docs/pages/es/installation/platforms.md | 5 +- docs/pages/es/installation/windows.md | 291 ++-- docs/pages/es/overview.md | 266 +-- docs/pages/es/project/CONTRIBUTING-gitflow.md | 131 ++ docs/pages/es/project/FAQ.md | 21 + docs/pages/es/project/ci-build-and-release.md | 206 +++ docs/pages/es/project/contributing.md | 205 +++ docs/pages/es/project/index.md | 62 +- docs/pages/es/project/releases.md | 1548 +++++++++-------- .../es/project/security-vulnerabilities.md | 79 + docs/pages/es/reference/index.md | 28 + .../pages/es/reference/mesheryctl-commands.md | 50 + 50 files changed, 3582 insertions(+), 1162 deletions(-) create mode 100644 docs/pages/es/404.md create mode 100644 docs/pages/es/archive.md create mode 100644 docs/pages/es/concepts/architecture/architecture.md create mode 100644 docs/pages/es/concepts/architecture/broker.md create mode 100644 docs/pages/es/concepts/architecture/database.md create mode 100644 docs/pages/es/concepts/architecture/meshsync.md create mode 100644 docs/pages/es/concepts/architecture/operator.md create mode 100644 docs/pages/es/concepts/architecture/service-meshes/adapters.md create mode 100644 docs/pages/es/concepts/architecture/service-meshes/index.md create mode 100644 docs/pages/es/concepts/index.md create mode 100644 docs/pages/es/extensibility/adapters.md create mode 100644 docs/pages/es/extensibility/api.md create mode 100644 docs/pages/es/extensibility/extensibility.md create mode 100644 docs/pages/es/extensibility/load-generators.md create mode 100644 docs/pages/es/extensibility/providers.md create mode 100644 docs/pages/es/getting-started/news.md create mode 100644 docs/pages/es/getting-started/overview.md create mode 100644 docs/pages/es/guides/index.md create mode 100644 docs/pages/es/guides/interpreting-performance-test-results.md create mode 100644 docs/pages/es/guides/meshery-metrics.md create mode 100644 docs/pages/es/guides/multiple-of-the-same-adapter.md create mode 100644 docs/pages/es/guides/sample-apps.md create mode 100644 docs/pages/es/guides/upgrade.md create mode 100644 docs/pages/es/guides/working-with-mesheryctl.md create mode 100644 docs/pages/es/project/FAQ.md create mode 100644 docs/pages/es/project/ci-build-and-release.md create mode 100644 docs/pages/es/reference/index.md create mode 100644 docs/pages/es/reference/mesheryctl-commands.md diff --git a/docs/pages/concepts/architecture/broker.md b/docs/pages/concepts/architecture/broker.md index e093f493394..8eda314aec6 100644 --- a/docs/pages/concepts/architecture/broker.md +++ b/docs/pages/concepts/architecture/broker.md @@ -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. diff --git a/docs/pages/es/404.md b/docs/pages/es/404.md new file mode 100644 index 00000000000..7fb0f59be80 --- /dev/null +++ b/docs/pages/es/404.md @@ -0,0 +1,27 @@ +--- +layout: page +title: 404 +permalink: es/404.html +language: es +lang: es +categories: es +excluded_in_search: true +display-title: "false" +--- + + +
+

+

Las cosas tienden a enREDarse por aquí...

+
Por favor reportar este issue (¡Gracias!) y regresar a la Documentaión de Meshery .
+
+ \ No newline at end of file diff --git a/docs/pages/es/archive.md b/docs/pages/es/archive.md new file mode 100644 index 00000000000..7a5837a8a27 --- /dev/null +++ b/docs/pages/es/archive.md @@ -0,0 +1,21 @@ +--- +layout: page +title: Artículos +permalink: es/archive/ +language: es +lang: es +categories: 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 %}

{{this_year}}

+{% else %}{% if this_year != next_year %} + +

{{next_year}}

+