From 106895327356f3bae0b60f25897a5a6459605004 Mon Sep 17 00:00:00 2001
From: Tyler Helmuth <12352919+TylerHelmuth@users.noreply.github.com>
Date: Mon, 17 Jul 2023 15:24:35 -0600
Subject: [PATCH 1/8] Add Collector helm chart docs

---
 .../kubernetes/{helm.md => helm/_index.md}    |   2 +-
 content/en/docs/kubernetes/helm/collector.md  | 384 ++++++++++++++++++
 static/refcache.json                          |   4 +
 3 files changed, 389 insertions(+), 1 deletion(-)
 rename content/en/docs/kubernetes/{helm.md => helm/_index.md} (92%)
 create mode 100644 content/en/docs/kubernetes/helm/collector.md

diff --git a/content/en/docs/kubernetes/helm.md b/content/en/docs/kubernetes/helm/_index.md
similarity index 92%
rename from content/en/docs/kubernetes/helm.md
rename to content/en/docs/kubernetes/helm/_index.md
index e120e5c0094c..a49182ba35d9 100644
--- a/content/en/docs/kubernetes/helm.md
+++ b/content/en/docs/kubernetes/helm/_index.md
@@ -13,7 +13,7 @@ to manage installs of the [OpenTelemetry Collector](/docs/collector),
 [OpenTelemetry Operator](/docs/kubernetes/operator), and
 [OpenTelemetry Demo](/docs/demo).
 
-Add OpenTelemetry Helm repository:
+Add the OpenTelemetry Helm repository with:
 
 ```
 helm repo add open-telemetry https://open-telemetry.github.io/opentelemetry-helm-charts
diff --git a/content/en/docs/kubernetes/helm/collector.md b/content/en/docs/kubernetes/helm/collector.md
new file mode 100644
index 000000000000..685f40aa7808
--- /dev/null
+++ b/content/en/docs/kubernetes/helm/collector.md
@@ -0,0 +1,384 @@
+---
+title: OpenTelemetry Collector Chart
+linkTitle: Collector Chart
+spelling:
+  cSpell:ignore statefulset kuberenetes filelogreceiver loggingexporter
+  cSpell:ignore filelogreceiver otlphttp sattributesprocessor kubelet
+  cSpell:ignore kubeletstatsreceiver sclusterreceiver sobjectsreceiver
+  cSpell:ignore hostmetricsreceiver
+---
+
+## Introduction
+
+The [OpenTelemetry Collector](/docs/collector) is an important tool for
+monitoring a Kubernetes cluster and all the services that in within. To
+facilitate installation and management of a Collector deployment in a Kubernetes
+the OpenTelemetry community created the
+[OpenTelemetry Collector Helm Chart](https://github.com/open-telemetry/opentelemetry-helm-charts/tree/main/charts/opentelemetry-collector).
+This helm chart can be used to install a Collector as a Deployment, Daemonset,
+or Statefulset.
+
+### Installing the Chart
+
+To install the chart with the release name `my-opentelemetry-collector``, run
+the following commands:
+
+```console
+helm repo add open-telemetry https://open-telemetry.github.io/opentelemetry-helm-charts
+helm install my-opentelemetry-collector open-telemetry/opentelemetry-collector --set mode=<daemonset|deployment|statefulset>
+```
+
+### Configuration
+
+The Collector chart requires that `mode` be set. `mode` can be either
+`daemonset`, `deployment`, or `statefulset` depending on which kind of
+Kubernetes deployment your use case requires.
+
+When installed, the chart provides a few default collector components to get
+your started. By default, the collector's config will look like:
+
+```yaml
+exporters:
+  logging: {}
+extensions:
+  health_check: {}
+  memory_ballast:
+    size_in_percentage: 40
+processors:
+  batch: {}
+  memory_limiter:
+    check_interval: 5s
+    limit_percentage: 80
+    spike_limit_percentage: 25
+receivers:
+  jaeger:
+    protocols:
+      grpc:
+        endpoint: ${env:MY_POD_IP}:14250
+      thrift_compact:
+        endpoint: ${env:MY_POD_IP}:6831
+      thrift_http:
+        endpoint: ${env:MY_POD_IP}:14268
+  otlp:
+    protocols:
+      grpc:
+        endpoint: ${env:MY_POD_IP}:4317
+      http:
+        endpoint: ${env:MY_POD_IP}:4318
+  prometheus:
+    config:
+      scrape_configs:
+        - job_name: opentelemetry-collector
+          scrape_interval: 10s
+          static_configs:
+            - targets:
+                - ${env:MY_POD_IP}:8888
+  zipkin:
+    endpoint: ${env:MY_POD_IP}:9411
+service:
+  extensions:
+    - health_check
+    - memory_ballast
+  pipelines:
+    logs:
+      exporters:
+        - logging
+      processors:
+        - memory_limiter
+        - batch
+      receivers:
+        - otlp
+    metrics:
+      exporters:
+        - logging
+      processors:
+        - memory_limiter
+        - batch
+      receivers:
+        - otlp
+        - prometheus
+    traces:
+      exporters:
+        - logging
+      processors:
+        - memory_limiter
+        - batch
+      receivers:
+        - otlp
+        - jaeger
+        - zipkin
+  telemetry:
+    metrics:
+      address: ${env:MY_POD_IP}:8888
+```
+
+The chart will also enable ports based on the default receivers. Default
+configuration can be removed by setting the value to `null` in your
+`values.yaml`. Ports can be disabled in the `values.yaml` as well.
+
+You can add/modify any part of the configuration using the `config` section in
+your `values.yaml`. When changing a pipeline, you must explicitly list all the
+components that are in the pipeline, including any default components.
+
+For example, to disable metrics and logging pipelines and non-otlp receivers:
+
+```yaml
+config:
+  receivers:
+    jaeger: null
+    prometheus: null
+    zipkin: null
+  service:
+    pipelines:
+      traces:
+        receivers:
+          - otlp
+      metrics: null
+      logs: null
+ports:
+  jaeger-compact:
+    enabled: false
+  jaeger-thrift:
+    enabled: false
+  jaeger-grpc:
+    enabled: false
+  zipkin:
+    enabled: false
+```
+
+All the configuration options (with comments) available in the chart can be view
+in its
+[values.yaml file](https://github.com/open-telemetry/opentelemetry-helm-charts/blob/main/charts/opentelemetry-collector/values.yaml).
+
+### Presets
+
+Many of the important components the Collector uses to monitor Kubernetes
+require special setup in the Collector's own Kuberenetes deployment. In order to
+make using these components easier, the Collector chart comes with some presets
+that, when enabled, handle the complex setup for these important components.
+
+Presets should be used as a starting point. They configure basic, but rich,
+functionality for their related components. If your use case requires extra
+configuration of these components it is recommend to NOT use the preset and
+instead manually configure the component and anything it requires (volumes,
+RBAC, etc.).
+
+#### Logs Collection Preset
+
+The collector can be used to collect logs sent to standard output by Kubernetes
+containers.
+
+This feature is disabled by default. It has the following requirements in order
+to be safely enabled:
+
+- It requires the
+  [`filelogreceiver`](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/filelogreceiver)
+  be included in the Collector image, such as the
+  [Contrib distribution of the Collector](https://github.com/open-telemetry/opentelemetry-collector-releases/pkgs/container/opentelemetry-collector-releases%2Fopentelemetry-collector-contrib).
+- Although not a strict requirement, it is recommended this preset be used with
+  `mode=daemonset`. The `filelogreceiver` will only be able to collect logs on
+  the node the Collector is running and multiple configured Collectors on the
+  same node will produce duplicate data.
+
+To enable this feature, set the `presets.logsCollection.enabled` property to
+`true`. When enabled, the chart will add a `filelogreceiver` to the `logs`
+pipeline. This receiver is configured to read the files where Kubernetes
+container runtime writes all containers' console output
+(`/var/log/pods/*/*/*.log`).
+
+Here is an example `values.yaml`:
+
+```yaml
+mode: daemonset
+presets:
+  logsCollection:
+    enabled: true
+```
+
+The chart's default logs pipeline uses the `loggingexporter`. Paired with the
+`logsCollection` preset's `filelogreceiver` it is easy to accidentally feed the
+exported logs back into the Collector, which can cause a "log explosion".
+
+To prevent the looping, the default configuration of the receiver excludes the
+Collector's own logs. If you want to include the collector's logs, make sure to
+replace the `logging` exporter with an exporter that does not send logs to
+collector's standard output.
+
+Here's an example `values.yaml` that replaces the default `logging` exporter on
+the `logs` pipeline with an `otlphttp` exporter that sends the container logs to
+`https://example.com:55681` endpoint. It also uses
+`presets.logsCollection.includeCollectorLogs` to tell the preset to enable
+collection of the Collector's logs.
+
+```yaml
+mode: daemonset
+
+presets:
+  logsCollection:
+    enabled: true
+    includeCollectorLogs: true
+
+config:
+  exporters:
+    otlphttp:
+      endpoint: https://example.com:55681
+  service:
+    pipelines:
+      logs:
+        exporters:
+          - otlphttp
+```
+
+#### Kubernetes Attributes Preset
+
+The collector can be configured to add Kubernetes metadata, such as
+k8s.pod.name, k8s,namespace.name, and k8s.node.name, to logs, metrics and
+traces. It is highly recommended to use the preset, or enable the
+k8sattributesprocessor manually.
+
+Due to RBAC considerations, this feature is disabled by default. It has the
+following requirements:
+
+- It requires the
+  [`k8sattributesprocessor`](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/k8sattributesprocessor)
+  be included in the Collector image, such as the
+  [Contrib distribution of the Collector](https://github.com/open-telemetry/opentelemetry-collector-releases/pkgs/container/opentelemetry-collector-releases%2Fopentelemetry-collector-contrib).
+
+To enable this feature, set the `presets.kubernetesAttributes.enabled` property
+to `true`. When enabled, the chart will add the necessary RBAC roles to the
+ClusterRole and will add a `k8sattributesprocessor` to each enabled pipeline.
+
+Here is an example `values.yaml`:
+
+```yaml
+mode: daemonset
+presets:
+  kubernetesAttributes:
+    enabled: true
+```
+
+#### Kubelet Metrics Preset
+
+The Collector can be configured to collect Kubelet metrics.
+
+This feature is disabled by default. It has the following requirements:
+
+- It requires the
+  [`kubeletstatsreceiver`](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/kubeletstatsreceiver)
+  be included in the Collector image, such as the
+  [Contrib distribution of the Collector](https://github.com/open-telemetry/opentelemetry-collector-releases/pkgs/container/opentelemetry-collector-releases%2Fopentelemetry-collector-contrib).
+- Although not a strict requirement, it is recommended this preset be used with
+  `mode=daemonset`. The `kubeletstatsreceiver` will only be able to collect
+  metrics on the node the Collector is running and multiple configured
+  Collectors on the same node will produce duplicate data.
+
+To enable this feature, set the `presets.kubeletMetrics.enabled` property to
+`true`. When enabled, the chart will add the necessary RBAC roles to the
+ClusterRole and will add a `kubeletstatsreceiver` to the metrics pipeline.
+
+Here is an example `values.yaml`:
+
+```yaml
+mode: daemonset
+presets:
+  kubeletMetrics:
+    enabled: true
+```
+
+#### Cluster Metrics Preset
+
+The collector can be configured to collect cluster-level metrics from the
+Kubernetes API server. These metrics include many of the metrics collected by
+Kube State Metrics.
+
+This feature is disabled by default. It has the following requirements:
+
+- It requires the
+  [`k8sclusterreceiver`](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/k8sclusterreceiver)
+  be included in the Collector image, such as the
+  [Contrib distribution of the Collector](https://github.com/open-telemetry/opentelemetry-collector-releases/pkgs/container/opentelemetry-collector-releases%2Fopentelemetry-collector-contrib).
+- Although not a strict requirement, it is recommended this preset be used with
+  `mode=deployment` or `mode=statefulset` with a single replica. Running
+  `k8sclusterreceiver` on multiple Collectors will produce duplicate data.
+
+To enable this feature, set the `presets.clusterMetrics.enabled` property to
+`true`. When enabled, the chart will add the necessary RBAC roles to the
+ClusterRole and will add a `k8sclusterreceiver` to the metrics pipeline.
+
+Here is an example `values.yaml`:
+
+```yaml
+mode: deployment
+replicaCount: 1
+presets:
+  clusterMetrics:
+    enabled: true
+```
+
+#### Kubernetes Events Preset
+
+The collector can be configured to collect Kubernetes events.
+
+This feature is disabled by default. It has the following requirements:
+
+- It requires the
+  [`k8sobjectsreceiver`](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/k8sobjectsreceiver)
+  be included in the Collector image, such as the
+  [Contrib distribution of the Collector](https://github.com/open-telemetry/opentelemetry-collector-releases/pkgs/container/opentelemetry-collector-releases%2Fopentelemetry-collector-contrib).
+- Although not a strict requirement, it is recommended this preset be used with
+  `mode=deployment` or `mode=statefulset` with a single replica. Running
+  `k8sclusterreceiver` on multiple Collectors will produce duplicate data.
+
+To enable this feature, set the `presets.kubernetesEvents.enabled` property to
+`true`. When enabled, the chart will add the necessary RBAC roles to the
+ClusterRole and will add a `k8sobjectsreceiver` to the logs pipeline configure
+to only collector events.
+
+Here is an example `values.yaml`:
+
+```yaml
+mode: deployment
+replicaCount: 1
+presets:
+  kubernetesEvents:
+    enabled: true
+```
+
+#### Host Metrics Preset
+
+The collector can be configured to collect host metrics from Kubernetes nodes.
+
+This feature is disabled by default. It has the following requirements:
+
+- It requires the
+  [`hostmetricsreceiver`](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/hostmetricsreceiver)
+  be included in the Collector image, such as the
+  [Contrib distribution of the Collector](https://github.com/open-telemetry/opentelemetry-collector-releases/pkgs/container/opentelemetry-collector-releases%2Fopentelemetry-collector-contrib).
+- Although not a strict requirement, it is recommended this preset be used with
+  `mode=daemonset`. The `hostmetricsreceiver` will only be able to collect
+  metrics on the node the Collector is running and multiple configured
+  Collectors on the same node will produce duplicate data.
+
+To enable this feature, set the `presets.hostMetrics.enabled` property to
+`true`. When enabled, the chart will add the necessary volumes and volumeMounts
+and will add a `hostmetricsreceiver` to the metrics pipeline. By default metrics
+will be scrapped every 10 seconds and the following scrappers are enabled:
+
+- cpu
+- load:
+- memory:
+- disk:
+- filesystem\*
+- network
+
+\*due to some overlap with the kubeletMetrics preset some filesystem types and
+mount points are excluded by default.
+
+Here is an example `values.yaml`:
+
+```yaml
+mode: daemonset
+presets:
+  hostMetrics:
+    enabled: true
+```
diff --git a/static/refcache.json b/static/refcache.json
index 4aab5091bb58..5fee741de0ea 100644
--- a/static/refcache.json
+++ b/static/refcache.json
@@ -2163,6 +2163,10 @@
     "StatusCode": 200,
     "LastSeen": "2023-07-01T14:29:53.746821-04:00"
   },
+  "https://github.com/open-telemetry/opentelemetry-collector-releases/pkgs/container/opentelemetry-collector-releases%2Fopentelemetry-collector-contrib": {
+    "StatusCode": 200,
+    "LastSeen": "2023-07-17T15:32:21.480243-06:00"
+  },
   "https://github.com/open-telemetry/opentelemetry-collector-releases/releases": {
     "StatusCode": 200,
     "LastSeen": "2023-06-30T08:44:01.99613-04:00"

From e5f2c9a8fe1543b0bf791f2898685b9ec4226e6c Mon Sep 17 00:00:00 2001
From: Tyler Helmuth <12352919+TylerHelmuth@users.noreply.github.com>
Date: Mon, 17 Jul 2023 17:26:57 -0600
Subject: [PATCH 2/8] Apply suggestions from code review

Co-authored-by: Phillip Carter <pcarter@fastmail.com>
---
 content/en/docs/kubernetes/helm/collector.md | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/content/en/docs/kubernetes/helm/collector.md b/content/en/docs/kubernetes/helm/collector.md
index 685f40aa7808..53a83da26ac1 100644
--- a/content/en/docs/kubernetes/helm/collector.md
+++ b/content/en/docs/kubernetes/helm/collector.md
@@ -25,17 +25,18 @@ the following commands:
 
 ```console
 helm repo add open-telemetry https://open-telemetry.github.io/opentelemetry-helm-charts
-helm install my-opentelemetry-collector open-telemetry/opentelemetry-collector --set mode=<daemonset|deployment|statefulset>
+helm install my-opentelemetry-collector open-telemetry/opentelemetry-collector \
+   --set mode=<daemonset|deployment|statefulset>
 ```
 
 ### Configuration
 
-The Collector chart requires that `mode` be set. `mode` can be either
+The Collector chart requires that `mode` is set. `mode` can be either
 `daemonset`, `deployment`, or `statefulset` depending on which kind of
 Kubernetes deployment your use case requires.
 
 When installed, the chart provides a few default collector components to get
-your started. By default, the collector's config will look like:
+you started. By default, the collector's config will look like:
 
 ```yaml
 exporters:
@@ -232,7 +233,7 @@ config:
 #### Kubernetes Attributes Preset
 
 The collector can be configured to add Kubernetes metadata, such as
-k8s.pod.name, k8s,namespace.name, and k8s.node.name, to logs, metrics and
+`k8s.pod.name`, `k8s,namespace.name`, and `k8s.node.name`, to logs, metrics and
 traces. It is highly recommended to use the preset, or enable the
 k8sattributesprocessor manually.
 

From 8167629c5b24b246d4950bd76645b0b3aaeb90be Mon Sep 17 00:00:00 2001
From: Tyler Helmuth <12352919+TylerHelmuth@users.noreply.github.com>
Date: Mon, 17 Jul 2023 17:28:02 -0600
Subject: [PATCH 3/8] Apply feedback

---
 content/en/docs/kubernetes/helm/collector.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/content/en/docs/kubernetes/helm/collector.md b/content/en/docs/kubernetes/helm/collector.md
index 53a83da26ac1..5ffe4f119c94 100644
--- a/content/en/docs/kubernetes/helm/collector.md
+++ b/content/en/docs/kubernetes/helm/collector.md
@@ -35,8 +35,8 @@ The Collector chart requires that `mode` is set. `mode` can be either
 `daemonset`, `deployment`, or `statefulset` depending on which kind of
 Kubernetes deployment your use case requires.
 
-When installed, the chart provides a few default collector components to get
-you started. By default, the collector's config will look like:
+When installed, the chart provides a few default collector components to get you
+started. By default, the collector's config will look like:
 
 ```yaml
 exporters:
@@ -366,9 +366,9 @@ and will add a `hostmetricsreceiver` to the metrics pipeline. By default metrics
 will be scrapped every 10 seconds and the following scrappers are enabled:
 
 - cpu
-- load:
-- memory:
-- disk:
+- load
+- memory
+- disk
 - filesystem\*
 - network
 

From 93b436d65dbb316cbee9a5e3f645444812ed9372 Mon Sep 17 00:00:00 2001
From: Tyler Helmuth <12352919+TylerHelmuth@users.noreply.github.com>
Date: Mon, 17 Jul 2023 19:13:14 -0600
Subject: [PATCH 4/8] Update codeowners

---
 .github/CODEOWNERS | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS
index 35b5b2d175cf..629990aebc08 100644
--- a/.github/CODEOWNERS
+++ b/.github/CODEOWNERS
@@ -35,6 +35,7 @@ content/en/docs/instrumentation/python/  @open-telemetry/docs-approvers @open-te
 content/en/docs/instrumentation/ruby/    @open-telemetry/docs-approvers @open-telemetry/ruby-approvers @open-telemetry/ruby-contrib-approvers
 content/en/docs/instrumentation/rust/    @open-telemetry/docs-approvers @open-telemetry/rust-approvers
 content/en/docs/instrumentation/swift/   @open-telemetry/docs-approvers @open-telemetry/swift-approvers
-content/en/docs/k8s-operator             @open-telemetry/docs-approvers @open-telemetry/operator-approvers
+content/en/docs/kubernetes/operator/     @open-telemetry/docs-approvers @open-telemetry/operator-approvers
+content/en/docs/kubernetes/helm/         @open-telemetry/docs-approvers @open-telemetry/helm-approvers
 content/en/docs/specs/                   @open-telemetry/docs-approvers @open-telemetry/specs-approvers
 content/en/ecosystem/demo/               @open-telemetry/demo-approvers @open-telemetry/demo-approvers

From 8a2f489f00f831f6962b858e2efea1bfca644ce1 Mon Sep 17 00:00:00 2001
From: Tyler Helmuth <12352919+TylerHelmuth@users.noreply.github.com>
Date: Mon, 17 Jul 2023 19:34:37 -0600
Subject: [PATCH 5/8] fix lint

---
 static/refcache.json | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/static/refcache.json b/static/refcache.json
index 5fee741de0ea..14336cd9ca87 100644
--- a/static/refcache.json
+++ b/static/refcache.json
@@ -4087,6 +4087,10 @@
     "StatusCode": 206,
     "LastSeen": "2023-06-29T18:42:56.97152-04:00"
   },
+  "https://sentry.io/for/opentelemetry/": {
+    "StatusCode": 200,
+    "LastSeen": "2023-07-17T19:34:01.098567-06:00"
+  },
   "https://sentrysoftware.com": {
     "StatusCode": 206,
     "LastSeen": "2023-06-30T16:27:00.258988-04:00"

From d310c19223b5b4b9b430f212c701fa169b601a41 Mon Sep 17 00:00:00 2001
From: Tyler Helmuth <12352919+TylerHelmuth@users.noreply.github.com>
Date: Tue, 18 Jul 2023 08:24:08 -0600
Subject: [PATCH 6/8] Apply suggestions from code review

Co-authored-by: Severin Neumann <severin.neumann@altmuehlnet.de>
---
 content/en/docs/kubernetes/helm/_index.md    |  2 +-
 content/en/docs/kubernetes/helm/collector.md | 36 ++++++++++----------
 2 files changed, 19 insertions(+), 19 deletions(-)

diff --git a/content/en/docs/kubernetes/helm/_index.md b/content/en/docs/kubernetes/helm/_index.md
index a49182ba35d9..29cc1ec86d82 100644
--- a/content/en/docs/kubernetes/helm/_index.md
+++ b/content/en/docs/kubernetes/helm/_index.md
@@ -15,6 +15,6 @@ to manage installs of the [OpenTelemetry Collector](/docs/collector),
 
 Add the OpenTelemetry Helm repository with:
 
-```
+```sh
 helm repo add open-telemetry https://open-telemetry.github.io/opentelemetry-helm-charts
 ```
diff --git a/content/en/docs/kubernetes/helm/collector.md b/content/en/docs/kubernetes/helm/collector.md
index 5ffe4f119c94..f5fe4d9b058e 100644
--- a/content/en/docs/kubernetes/helm/collector.md
+++ b/content/en/docs/kubernetes/helm/collector.md
@@ -12,18 +12,18 @@ spelling:
 
 The [OpenTelemetry Collector](/docs/collector) is an important tool for
 monitoring a Kubernetes cluster and all the services that in within. To
-facilitate installation and management of a Collector deployment in a Kubernetes
+facilitate installation and management of a collector deployment in a Kubernetes
 the OpenTelemetry community created the
 [OpenTelemetry Collector Helm Chart](https://github.com/open-telemetry/opentelemetry-helm-charts/tree/main/charts/opentelemetry-collector).
-This helm chart can be used to install a Collector as a Deployment, Daemonset,
+This helm chart can be used to install a collector as a Deployment, Daemonset,
 or Statefulset.
 
 ### Installing the Chart
 
-To install the chart with the release name `my-opentelemetry-collector``, run
+To install the chart with the release name `my-opentelemetry-collector`, run
 the following commands:
 
-```console
+```sh
 helm repo add open-telemetry https://open-telemetry.github.io/opentelemetry-helm-charts
 helm install my-opentelemetry-collector open-telemetry/opentelemetry-collector \
    --set mode=<daemonset|deployment|statefulset>
@@ -31,7 +31,7 @@ helm install my-opentelemetry-collector open-telemetry/opentelemetry-collector \
 
 ### Configuration
 
-The Collector chart requires that `mode` is set. `mode` can be either
+The OpenTelemetry Collector Chart requires that `mode` is set. `mode` can be either
 `daemonset`, `deployment`, or `statefulset` depending on which kind of
 Kubernetes deployment your use case requires.
 
@@ -153,9 +153,9 @@ in its
 
 ### Presets
 
-Many of the important components the Collector uses to monitor Kubernetes
+Many of the important components the OpenTelemetry Collector uses to monitor Kubernetes
 require special setup in the Collector's own Kuberenetes deployment. In order to
-make using these components easier, the Collector chart comes with some presets
+make using these components easier, the OpenTelemetry Collector Chart comes with some presets
 that, when enabled, handle the complex setup for these important components.
 
 Presets should be used as a starting point. They configure basic, but rich,
@@ -166,7 +166,7 @@ RBAC, etc.).
 
 #### Logs Collection Preset
 
-The collector can be used to collect logs sent to standard output by Kubernetes
+The OpenTelemetry Collector can be used to collect logs sent to standard output by Kubernetes
 containers.
 
 This feature is disabled by default. It has the following requirements in order
@@ -198,10 +198,10 @@ presets:
 
 The chart's default logs pipeline uses the `loggingexporter`. Paired with the
 `logsCollection` preset's `filelogreceiver` it is easy to accidentally feed the
-exported logs back into the Collector, which can cause a "log explosion".
+exported logs back into the collector, which can cause a "log explosion".
 
 To prevent the looping, the default configuration of the receiver excludes the
-Collector's own logs. If you want to include the collector's logs, make sure to
+collector's own logs. If you want to include the collector's logs, make sure to
 replace the `logging` exporter with an exporter that does not send logs to
 collector's standard output.
 
@@ -209,7 +209,7 @@ Here's an example `values.yaml` that replaces the default `logging` exporter on
 the `logs` pipeline with an `otlphttp` exporter that sends the container logs to
 `https://example.com:55681` endpoint. It also uses
 `presets.logsCollection.includeCollectorLogs` to tell the preset to enable
-collection of the Collector's logs.
+collection of the collector's logs.
 
 ```yaml
 mode: daemonset
@@ -232,10 +232,10 @@ config:
 
 #### Kubernetes Attributes Preset
 
-The collector can be configured to add Kubernetes metadata, such as
-`k8s.pod.name`, `k8s,namespace.name`, and `k8s.node.name`, to logs, metrics and
+The OpenTelemetry Collector can be configured to add Kubernetes metadata, such as
+`k8s.pod.name`, `k8s.namespace.name`, and `k8s.node.name`, to logs, metrics and
 traces. It is highly recommended to use the preset, or enable the
-k8sattributesprocessor manually.
+`k8sattributesprocessor` manually.
 
 Due to RBAC considerations, this feature is disabled by default. It has the
 following requirements:
@@ -260,7 +260,7 @@ presets:
 
 #### Kubelet Metrics Preset
 
-The Collector can be configured to collect Kubelet metrics.
+The OpenTelemetry Collector can be configured to collect Kubelet metrics.
 
 This feature is disabled by default. It has the following requirements:
 
@@ -288,7 +288,7 @@ presets:
 
 #### Cluster Metrics Preset
 
-The collector can be configured to collect cluster-level metrics from the
+The OpenTelemetry Collector can be configured to collect cluster-level metrics from the
 Kubernetes API server. These metrics include many of the metrics collected by
 Kube State Metrics.
 
@@ -318,7 +318,7 @@ presets:
 
 #### Kubernetes Events Preset
 
-The collector can be configured to collect Kubernetes events.
+The OpenTelemetry Collector can be configured to collect Kubernetes events.
 
 This feature is disabled by default. It has the following requirements:
 
@@ -347,7 +347,7 @@ presets:
 
 #### Host Metrics Preset
 
-The collector can be configured to collect host metrics from Kubernetes nodes.
+The OpenTelemetry Collector can be configured to collect host metrics from Kubernetes nodes.
 
 This feature is disabled by default. It has the following requirements:
 

From e079d19d7f61b994249d40d7b384541664094c06 Mon Sep 17 00:00:00 2001
From: Tyler Helmuth <12352919+TylerHelmuth@users.noreply.github.com>
Date: Tue, 18 Jul 2023 08:25:04 -0600
Subject: [PATCH 7/8] apply feedback

---
 content/en/docs/kubernetes/helm/collector.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/content/en/docs/kubernetes/helm/collector.md b/content/en/docs/kubernetes/helm/collector.md
index f5fe4d9b058e..6ba4885fa4f8 100644
--- a/content/en/docs/kubernetes/helm/collector.md
+++ b/content/en/docs/kubernetes/helm/collector.md
@@ -369,12 +369,9 @@ will be scrapped every 10 seconds and the following scrappers are enabled:
 - load
 - memory
 - disk
-- filesystem\*
+- filesystem[^1]
 - network
 
-\*due to some overlap with the kubeletMetrics preset some filesystem types and
-mount points are excluded by default.
-
 Here is an example `values.yaml`:
 
 ```yaml
@@ -383,3 +380,6 @@ presets:
   hostMetrics:
     enabled: true
 ```
+
+[^1] due to some overlap with the kubeletMetrics preset some filesystem types and
+mount points are excluded by default.

From ea238a78e441af8656a07c57b4c40024ab243ff8 Mon Sep 17 00:00:00 2001
From: Tyler Helmuth <12352919+TylerHelmuth@users.noreply.github.com>
Date: Tue, 18 Jul 2023 08:42:30 -0600
Subject: [PATCH 8/8] fix format

---
 content/en/docs/kubernetes/helm/collector.md | 40 ++++++++++----------
 1 file changed, 21 insertions(+), 19 deletions(-)

diff --git a/content/en/docs/kubernetes/helm/collector.md b/content/en/docs/kubernetes/helm/collector.md
index 6ba4885fa4f8..9756417d96e9 100644
--- a/content/en/docs/kubernetes/helm/collector.md
+++ b/content/en/docs/kubernetes/helm/collector.md
@@ -20,8 +20,8 @@ or Statefulset.
 
 ### Installing the Chart
 
-To install the chart with the release name `my-opentelemetry-collector`, run
-the following commands:
+To install the chart with the release name `my-opentelemetry-collector`, run the
+following commands:
 
 ```sh
 helm repo add open-telemetry https://open-telemetry.github.io/opentelemetry-helm-charts
@@ -31,8 +31,8 @@ helm install my-opentelemetry-collector open-telemetry/opentelemetry-collector \
 
 ### Configuration
 
-The OpenTelemetry Collector Chart requires that `mode` is set. `mode` can be either
-`daemonset`, `deployment`, or `statefulset` depending on which kind of
+The OpenTelemetry Collector Chart requires that `mode` is set. `mode` can be
+either `daemonset`, `deployment`, or `statefulset` depending on which kind of
 Kubernetes deployment your use case requires.
 
 When installed, the chart provides a few default collector components to get you
@@ -153,10 +153,11 @@ in its
 
 ### Presets
 
-Many of the important components the OpenTelemetry Collector uses to monitor Kubernetes
-require special setup in the Collector's own Kuberenetes deployment. In order to
-make using these components easier, the OpenTelemetry Collector Chart comes with some presets
-that, when enabled, handle the complex setup for these important components.
+Many of the important components the OpenTelemetry Collector uses to monitor
+Kubernetes require special setup in the Collector's own Kuberenetes deployment.
+In order to make using these components easier, the OpenTelemetry Collector
+Chart comes with some presets that, when enabled, handle the complex setup for
+these important components.
 
 Presets should be used as a starting point. They configure basic, but rich,
 functionality for their related components. If your use case requires extra
@@ -166,8 +167,8 @@ RBAC, etc.).
 
 #### Logs Collection Preset
 
-The OpenTelemetry Collector can be used to collect logs sent to standard output by Kubernetes
-containers.
+The OpenTelemetry Collector can be used to collect logs sent to standard output
+by Kubernetes containers.
 
 This feature is disabled by default. It has the following requirements in order
 to be safely enabled:
@@ -232,9 +233,9 @@ config:
 
 #### Kubernetes Attributes Preset
 
-The OpenTelemetry Collector can be configured to add Kubernetes metadata, such as
-`k8s.pod.name`, `k8s.namespace.name`, and `k8s.node.name`, to logs, metrics and
-traces. It is highly recommended to use the preset, or enable the
+The OpenTelemetry Collector can be configured to add Kubernetes metadata, such
+as `k8s.pod.name`, `k8s.namespace.name`, and `k8s.node.name`, to logs, metrics
+and traces. It is highly recommended to use the preset, or enable the
 `k8sattributesprocessor` manually.
 
 Due to RBAC considerations, this feature is disabled by default. It has the
@@ -288,9 +289,9 @@ presets:
 
 #### Cluster Metrics Preset
 
-The OpenTelemetry Collector can be configured to collect cluster-level metrics from the
-Kubernetes API server. These metrics include many of the metrics collected by
-Kube State Metrics.
+The OpenTelemetry Collector can be configured to collect cluster-level metrics
+from the Kubernetes API server. These metrics include many of the metrics
+collected by Kube State Metrics.
 
 This feature is disabled by default. It has the following requirements:
 
@@ -347,7 +348,8 @@ presets:
 
 #### Host Metrics Preset
 
-The OpenTelemetry Collector can be configured to collect host metrics from Kubernetes nodes.
+The OpenTelemetry Collector can be configured to collect host metrics from
+Kubernetes nodes.
 
 This feature is disabled by default. It has the following requirements:
 
@@ -381,5 +383,5 @@ presets:
     enabled: true
 ```
 
-[^1] due to some overlap with the kubeletMetrics preset some filesystem types and
-mount points are excluded by default.
+[^1] due to some overlap with the kubeletMetrics preset some filesystem types
+and mount points are excluded by default.