From 6eadf2cdea872c279a0ecf9dd1ed8c9d9a2debdb Mon Sep 17 00:00:00 2001 From: Mario Macias Date: Tue, 7 May 2024 12:31:17 +0200 Subject: [PATCH] make vale happy --- docs/sources/setup/kubernetes-helm.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/sources/setup/kubernetes-helm.md b/docs/sources/setup/kubernetes-helm.md index 6766fe052..c03c7cfc2 100644 --- a/docs/sources/setup/kubernetes-helm.md +++ b/docs/sources/setup/kubernetes-helm.md @@ -102,7 +102,7 @@ podAnnotations: prometheus.io/port: '9090' ``` -Analogously, the Helm chart allows overriding names, labels and annotations for +Analogously, the Helm chart allows overriding names, labels, and annotations for multiple resources that are involved in the deployment of Beyla, such as service accounts, cluster roles, security contexts, etc. The [Beyla Helm chart documentation](https://github.com/grafana/beyla/blob/main/charts/beyla/README.md) @@ -117,7 +117,7 @@ OpenTelemetry Endpoint, you need to provide the credentials via the The recommended way is to store such value in a Kubernetes Secret and then specify the environment variable referring to it from the Helm configuration. -For example, create and deploy the following secret: +For example, deploy the following secret: ``` apiVersion: v1