Skip to content

Commit 09dee1f

Browse files
chalinchalin
committed
Fix format
1 parent fc31df7 commit 09dee1f

File tree

11 files changed

+40
-33
lines changed

11 files changed

+40
-33
lines changed

‎content/en/blog/2025/otel-collector-k8s-discovery.md

+4-3
Original file line numberDiff line numberDiff line change
@@ -70,9 +70,10 @@ So, what if, as a Collector user, you could simply enable automatic discovery
7070
and then let your cluster users tell the Collector how their workloads should be
7171
monitored by annotating their pods properly? That sounds awesome, and it’s not
7272
actually something new. OpenTelemetry already supports auto-instrumentation
73-
through the [Kubernetes operator](/docs/platforms/kubernetes/operator/automatic/),
74-
allowing users to instrument their applications automatically just by annotating
75-
their pods. In addition, this is a feature that other monitoring agents in the
73+
through the
74+
[Kubernetes operator](/docs/platforms/kubernetes/operator/automatic/), allowing
75+
users to instrument their applications automatically just by annotating their
76+
pods. In addition, this is a feature that other monitoring agents in the
7677
observability industry already support, and users are familiar with it.
7778

7879
All this motivation led the OpenTelemetry community

‎content/en/docs/collector/scaling.md

+6-6
Original file line numberDiff line numberDiff line change
@@ -139,9 +139,9 @@ load balancer. Using a Sidecar also makes sense to avoid bringing down a crucial
139139
component for all pods in a node when one DaemonSet pod fails.
140140

141141
The sidecar pattern consists in adding a container into the workload pod. The
142-
[OpenTelemetry Operator](/docs/platforms/kubernetes/operator/) can automatically add that
143-
for you. To accomplish that, you’ll need an OpenTelemetry Collector CR and
144-
you’ll need to annotate your PodSpec or Pod telling the operator to inject a
142+
[OpenTelemetry Operator](/docs/platforms/kubernetes/operator/) can automatically
143+
add that for you. To accomplish that, you’ll need an OpenTelemetry Collector CR
144+
and you’ll need to annotate your PodSpec or Pod telling the operator to inject a
145145
sidecar:
146146

147147
```yaml
@@ -244,9 +244,9 @@ Collector. For instance, each Collector could be responsible for one Kubernetes
244244
namespace or specific labels on the workloads.
245245
246246
Another way of scaling the Prometheus receiver is to use the
247-
[Target Allocator](/docs/platforms/kubernetes/operator/target-allocator/): it’s an extra
248-
binary that can be deployed as part of the OpenTelemetry Operator and will
249-
distribute Prometheus scrape targets for a given configuration across the
247+
[Target Allocator](/docs/platforms/kubernetes/operator/target-allocator/): it’s
248+
an extra binary that can be deployed as part of the OpenTelemetry Operator and
249+
will distribute Prometheus scrape targets for a given configuration across the
250250
cluster of Collectors. You can use a Custom Resource (CR) like the following to
251251
make use of the Target Allocator:
252252

‎content/en/docs/demo/kubernetes-deployment.md

+3-2
Original file line numberDiff line numberDiff line change
@@ -5,8 +5,9 @@ aliases: [kubernetes_deployment]
55
cSpell:ignore: loadgen otlphttp spanmetrics
66
---
77

8-
We provide a [OpenTelemetry Demo Helm chart](/docs/platforms/kubernetes/helm/demo/) to
9-
help deploy the demo to an existing Kubernetes cluster.
8+
We provide a
9+
[OpenTelemetry Demo Helm chart](/docs/platforms/kubernetes/helm/demo/) to help
10+
deploy the demo to an existing Kubernetes cluster.
1011

1112
[Helm](https://helm.sh) must be installed to use the charts. Please refer to
1213
Helm's [documentation](https://helm.sh/docs/) to get started.

‎content/en/docs/kubernetes/operator/troubleshooting/target-allocator.md

+6-5
Original file line numberDiff line numberDiff line change
@@ -4,11 +4,12 @@ cSpell:ignore: bleh targetallocator
44
---
55

66
If you’ve enabled
7-
[Target Allocator](/docs/platforms/kubernetes/operator/target-allocator/) service
8-
discovery on the [OpenTelemetry Operator](/docs/platforms/kubernetes/operator/), and the
9-
Target Allocator is failing to discover scrape targets, there are a few
10-
troubleshooting steps that you can take to help you understand what’s going on
11-
and restore normal operation.
7+
[Target Allocator](/docs/platforms/kubernetes/operator/target-allocator/)
8+
service discovery on the
9+
[OpenTelemetry Operator](/docs/platforms/kubernetes/operator/), and the Target
10+
Allocator is failing to discover scrape targets, there are a few troubleshooting
11+
steps that you can take to help you understand what’s going on and restore
12+
normal operation.
1213

1314
## Troubleshooting steps
1415

‎content/en/docs/platforms/kubernetes/helm/collector.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -170,8 +170,8 @@ This feature is disabled by default. It has the following requirements in order
170170
to be safely enabled:
171171

172172
- It requires the
173-
[Filelog receiver](/docs/platforms/kubernetes/collector/components/#filelog-receiver) be
174-
included in the Collector image, such as the
173+
[Filelog receiver](/docs/platforms/kubernetes/collector/components/#filelog-receiver)
174+
be included in the Collector image, such as the
175175
[Contrib distribution of the Collector](https://github.com/open-telemetry/opentelemetry-collector-releases/pkgs/container/opentelemetry-collector-releases%2Fopentelemetry-collector-contrib).
176176
- Although not a strict requirement, it is recommended this preset be used with
177177
`mode=daemonset`. The `filelogreceiver` will only be able to collect logs on

‎content/en/docs/platforms/kubernetes/helm/operator.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -5,8 +5,8 @@ linkTitle: Operator Chart
55

66
## Introduction
77

8-
The [OpenTelemetry Operator](/docs/platforms/kubernetes/operator) is a Kubernetes operator
9-
that manages [OpenTelemetry Collectors](/docs/collector) and
8+
The [OpenTelemetry Operator](/docs/platforms/kubernetes/operator) is a
9+
Kubernetes operator that manages [OpenTelemetry Collectors](/docs/collector) and
1010
auto-instrumentation of workloads. One of the ways to install the OpenTelemetry
1111
Operator is via the
1212
[OpenTelemetry Operator Helm Chart](https://github.com/open-telemetry/opentelemetry-helm-charts/tree/main/charts/opentelemetry-operator).

‎content/en/docs/platforms/kubernetes/operator/troubleshooting/automatic.md

+5-4
Original file line numberDiff line numberDiff line change
@@ -3,10 +3,11 @@ title: Auto-instrumentation
33
cSpell:ignore: PYTHONPATH
44
---
55

6-
If you're using the [OpenTelemetry Operator](/docs/platforms/kubernetes/operator)'s
7-
capability to inject [auto-instrumentation](/docs/platforms/kubernetes/operator/automatic)
8-
and you're not seeing any traces or metrics, follow these troubleshooting steps
9-
to understand what’s going on.
6+
If you're using the
7+
[OpenTelemetry Operator](/docs/platforms/kubernetes/operator)'s capability to
8+
inject [auto-instrumentation](/docs/platforms/kubernetes/operator/automatic) and
9+
you're not seeing any traces or metrics, follow these troubleshooting steps to
10+
understand what’s going on.
1011

1112
## Troubleshooting steps
1213

‎content/en/docs/platforms/kubernetes/operator/troubleshooting/target-allocator.md

+6-5
Original file line numberDiff line numberDiff line change
@@ -4,11 +4,12 @@ cSpell:ignore: bleh targetallocator
44
---
55

66
If you’ve enabled
7-
[Target Allocator](/docs/platforms/kubernetes/operator/target-allocator/) service
8-
discovery on the [OpenTelemetry Operator](/docs/platforms/kubernetes/operator/), and the
9-
Target Allocator is failing to discover scrape targets, there are a few
10-
troubleshooting steps that you can take to help you understand what’s going on
11-
and restore normal operation.
7+
[Target Allocator](/docs/platforms/kubernetes/operator/target-allocator/)
8+
service discovery on the
9+
[OpenTelemetry Operator](/docs/platforms/kubernetes/operator/), and the Target
10+
Allocator is failing to discover scrape targets, there are a few troubleshooting
11+
steps that you can take to help you understand what’s going on and restore
12+
normal operation.
1213

1314
## Troubleshooting steps
1415

‎content/en/docs/zero-code/_index.md

+2-1
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,7 @@ If you are using Kubernetes, you can use the [OpenTelemetry Operator for
1010
Kubernetes][otel-op] to [inject zero-code instrumentation] for .NET, Java,
1111
Node.js, Python, or Go into your application.
1212

13-
[inject zero-code instrumentation]: /docs/platforms/kubernetes/operator/automatic/
13+
[inject zero-code instrumentation]:
14+
/docs/platforms/kubernetes/operator/automatic/
1415
[zero-code instrumentation]: /docs/concepts/instrumentation/zero-code/
1516
[otel-op]: /docs/platforms/kubernetes/operator/

‎content/es/docs/concepts/components.md

+2-1
Original file line numberDiff line numberDiff line change
@@ -132,7 +132,8 @@ El Operador de OpenTelemetry es una implementación de un Operador de Kubernetes
132132
El operador gestiona el Collector de OpenTelemetry y la auto-instrumentación de
133133
las aplicaciones usando OpenTelemetry.
134134

135-
Para más información, consulta el [Operador K8s](/docs/platforms/kubernetes/operator/).
135+
Para más información, consulta el
136+
[Operador K8s](/docs/platforms/kubernetes/operator/).
136137

137138
## Elementos de Función como Servicio
138139

‎content/fr/docs/what-is-opentelemetry.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -81,8 +81,8 @@ OpenTelemetry se compose des principaux composants suivants :
8181
- Le [Collector OpenTelemetry](/docs/collector), un proxy qui reçoit, modifie et
8282
exporte les données de télémétrie
8383
- Divers autres outils, tels que
84-
l'[Opérateur Kubernetes pour OpenTelemetry](/docs/platforms/kubernetes/operator/), les
85-
[Helm Charts pour OpenTelemetry](/docs/platforms/kubernetes/helm/) et des
84+
l'[Opérateur Kubernetes pour OpenTelemetry](/docs/platforms/kubernetes/operator/),
85+
les [Helm Charts pour OpenTelemetry](/docs/platforms/kubernetes/helm/) et des
8686
[ressources communautaires pour les FaaS](/docs/platforms/faas/)
8787

8888
OpenTelemetry est utilisé par une grande variété de

0 commit comments

Comments
 (0)