Skip to content

[DOCS-12497] Add k8s persistence volume info #33007

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
+15 −1
Open

[DOCS-12497] Add k8s persistence volume info #33007

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ac9b7b6
add pv section
maycmlee Nov 21, 2025
e42ecca
small edits
maycmlee Nov 21, 2025
33cff76
add link to disk buffering
maycmlee Nov 21, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions content/en/observability_pipelines/configuration/install_the_worker/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -126,6 +126,8 @@ The Observability Pipelines Worker supports all major Kubernetes distributions,

See [Update Existing Pipelines][5] if you want to make changes to your pipeline's configuration.

**Note**: If you enable [disk buffering][6] for destinations, you can use Kubernetes [persistence volume][7] to handle back pressure when a destination is unavailable or can't keep up with the volume of data that the Worker is sending.

#### Self-hosted and self-managed Kubernetes clusters

If you are running a self-hosted and self-managed Kubernetes cluster, and defined zones with node labels using `topology.kubernetes.io/zone`, then you can use the Helm chart values file as is. However, if you are not using the label `topology.kubernetes.io/zone`, you need to update the `topologyKey` in the `values.yaml` file to match the key you are using. Or if you run your Kubernetes install without zones, remove the entire `topology.kubernetes.io/zone` section.
Expand All @@ -135,6 +137,8 @@ If you are running a self-hosted and self-managed Kubernetes cluster, and define
[3]: https://app.datadoghq.com/organization-settings/remote-config/setup
[4]: /observability_pipelines/environment_variables/
[5]: https://github.com/DataDog/helm-charts/blob/main/charts/observability-pipelines-worker/values.yaml
[6]: /observability_pipelines/scaling_and_performance/handling_load_and_backpressure/#disk-buffers
[7]: https://github.com/DataDog/helm-charts/blob/23624b6e49eef98e84b21689672bb63a7a5df48b/charts/observability-pipelines-worker/values.yaml#L268

{{% /tab %}}
{{% tab "Linux" %}}
Expand Down
6 changes: 6 additions & 0 deletions ...servability_pipelines/scaling_and_performance/handling_load_and_backpressure.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,6 +44,12 @@ Observability Pipelines destination's buffers are configured to block events, wh

Observability Pipelines destinations can be configured with disk buffers (in Preview). When disk buffering is enabled for a destination, every event is first sent through the buffer and written to the data files, before the data is sent to the downstream integration. By default, data is not synchronized for every write, but instead synchronized on an interval (500 milliseconds), which allows for high throughput with a reduced risk of data loss.

### Kubernetes persistence volume

If you enable disk buffering for destinations, you can use Kubernetes [persistence volume][1] to handle back pressure when a destination is unavailable or can't keep up with the volume of data that the Worker is sending.

## Further reading

{{< partial name="whats-next/whats-next.html" >}}

[1]: https://github.com/DataDog/helm-charts/blob/23624b6e49eef98e84b21689672bb63a7a5df48b/charts/observability-pipelines-worker/values.yaml#L268
6 changes: 5 additions & 1 deletion layouts/shortcodes/observability_pipelines/install_worker/kubernetes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,11 +37,15 @@ The Observability Pipelines Worker supports all major Kubernetes distributions,

See [Update Existing Pipelines][602] if you want to make changes to your pipeline's configuration.

**Note**: If you enable [disk buffering][605] for destinations, you can use Kubernetes [persistence volume][606] to handle back pressure when a destination is unavailable or can't keep up with the volume of data that the Worker is sending.

#### Self-hosted and self-managed Kubernetes clusters

If you are running a self-hosted and self-managed Kubernetes cluster, and defined zones with node labels using `topology.kubernetes.io/zone`, then you can use the Helm chart values file as is. However, if you are not using the label `topology.kubernetes.io/zone`, you need to update the `topologyKey` in the `values.yaml` file to match the key you are using. Or if you run your Kubernetes install without zones, remove the entire `topology.kubernetes.io/zone` section.

[601]: /resources/yaml/observability_pipelines/v2/setup/values.yaml
[602]: /observability_pipelines/update_existing_pipelines
[603]: https://github.com/DataDog/helm-charts/blob/main/charts/observability-pipelines-worker/values.yaml
[604]: https://app.datadoghq.com/organization-settings/remote-config/setup
[604]: https://app.datadoghq.com/organization-settings/remote-config/setup
[605]: /observability_pipelines/scaling_and_performance/handling_load_and_backpressure/#disk-buffers
[606]: https://github.com/DataDog/helm-charts/blob/23624b6e49eef98e84b21689672bb63a7a5df48b/charts/observability-pipelines-worker/values.yaml#L268
Loading