From 9fe390252e05d577d23a3703dc802274d1130190 Mon Sep 17 00:00:00 2001
From: Robby Milo <robbymilo@fastmail.com>
Date: Thu, 20 Feb 2025 17:01:35 +0100
Subject: [PATCH] docs - remove beta label (#7119)

* docs - remove beta label

* add public-preview label to convert.md
---
 docs/sources/flow/reference/cli/convert.md    |  4 +-
 .../reference/components/discovery.kubelet.md |  2 -
 .../flow/reference/components/loki.echo.md    |  2 -
 .../components/mimir.rules.kubernetes.md      |  2 -
 .../flow/reference/components/module.file.md  |  2 -
 .../flow/reference/components/module.git.md   |  2 -
 .../flow/reference/components/module.http.md  |  2 -
 .../reference/components/module.string.md     |  2 -
 .../otelcol.exporter.loadbalancing.md         | 46 +++++++++----------
 .../otelcol.processor.resourcedetection.md    |  6 +--
 .../otelcol.processor.tail_sampling.md        |  6 +--
 .../components/otelcol.receiver.loki.md       |  2 -
 .../components/otelcol.receiver.prometheus.md |  2 -
 .../prometheus.exporter.postgres.md           |  2 -
 .../components/prometheus.exporter.windows.md | 22 ++++-----
 .../prometheus.operator.podmonitors.md        |  2 -
 .../components/prometheus.operator.probes.md  |  2 -
 .../prometheus.operator.servicemonitors.md    |  2 -
 .../reference/components/pyroscope.ebpf.md    |  8 ++--
 .../reference/components/pyroscope.scrape.md  | 44 +++++++++---------
 .../reference/components/pyroscope.write.md   |  2 -
 .../reference/config-blocks/import.file.md    |  2 -
 .../flow/tasks/configure-agent-clustering.md  |  3 ++
 23 files changed, 66 insertions(+), 103 deletions(-)

diff --git a/docs/sources/flow/reference/cli/convert.md b/docs/sources/flow/reference/cli/convert.md
index 73761440eec4..444149eb3c35 100644
--- a/docs/sources/flow/reference/cli/convert.md
+++ b/docs/sources/flow/reference/cli/convert.md
@@ -7,7 +7,7 @@ aliases:
 canonical: https://grafana.com/docs/agent/latest/flow/reference/cli/convert/
 description: Learn about the convert command
 labels:
-  stage: beta
+  stage: public-preview
 menuTitle: convert
 title: The convert command
 weight: 100
@@ -136,4 +136,4 @@ Refer to [Migrate from Grafana Agent Static to {{< param "PRODUCT_NAME" >}}][mig
 [migrate-promtail]: ../../../tasks/migrate/from-promtail/
 [migrate-static]: ../../../tasks/migrate/from-static/
 [Grafana Agent Static]: ../../../../static/
-[integrations-next]: ../../../../static/configuration/integrations/integrations-next/
\ No newline at end of file
+[integrations-next]: ../../../../static/configuration/integrations/integrations-next/
diff --git a/docs/sources/flow/reference/components/discovery.kubelet.md b/docs/sources/flow/reference/components/discovery.kubelet.md
index f9fef4a85693..8abb79b12f20 100644
--- a/docs/sources/flow/reference/components/discovery.kubelet.md
+++ b/docs/sources/flow/reference/components/discovery.kubelet.md
@@ -6,8 +6,6 @@ aliases:
 - /docs/grafana-cloud/send-data/agent/flow/reference/components/discovery.kubelet/
 canonical: https://grafana.com/docs/agent/latest/flow/reference/components/discovery.kubelet/
 description: Learn about discovery.kubelet
-labels:
-  stage: beta
 title: discovery.kubelet
 ---
 
diff --git a/docs/sources/flow/reference/components/loki.echo.md b/docs/sources/flow/reference/components/loki.echo.md
index eb16448a8670..5e4747976dd4 100644
--- a/docs/sources/flow/reference/components/loki.echo.md
+++ b/docs/sources/flow/reference/components/loki.echo.md
@@ -6,8 +6,6 @@ aliases:
 - /docs/grafana-cloud/send-data/agent/flow/reference/components/loki.echo/
 canonical: https://grafana.com/docs/agent/latest/flow/reference/components/loki.echo/
 description: Learn about loki.echo
-labels:
-  stage: beta
 title: loki.echo
 ---
 
diff --git a/docs/sources/flow/reference/components/mimir.rules.kubernetes.md b/docs/sources/flow/reference/components/mimir.rules.kubernetes.md
index 17bb3c63fc37..fd25722de82f 100644
--- a/docs/sources/flow/reference/components/mimir.rules.kubernetes.md
+++ b/docs/sources/flow/reference/components/mimir.rules.kubernetes.md
@@ -6,8 +6,6 @@ aliases:
 - /docs/grafana-cloud/send-data/agent/flow/reference/components/mimir.rules.kubernetes/
 canonical: https://grafana.com/docs/agent/latest/flow/reference/components/mimir.rules.kubernetes/
 description: Learn about mimir.rules.kubernetes
-labels:
-  stage: beta
 title: mimir.rules.kubernetes
 ---
 
diff --git a/docs/sources/flow/reference/components/module.file.md b/docs/sources/flow/reference/components/module.file.md
index a16d5b8d23f7..cb1a90d878ee 100644
--- a/docs/sources/flow/reference/components/module.file.md
+++ b/docs/sources/flow/reference/components/module.file.md
@@ -6,8 +6,6 @@ aliases:
 - /docs/grafana-cloud/send-data/agent/flow/reference/components/module.file/
 canonical: https://grafana.com/docs/agent/latest/flow/reference/components/module.file/
 description: Learn about module.file
-labels:
-  stage: beta
 title: module.file
 ---
 
diff --git a/docs/sources/flow/reference/components/module.git.md b/docs/sources/flow/reference/components/module.git.md
index 98544a13f2fe..2087dc7b99c5 100644
--- a/docs/sources/flow/reference/components/module.git.md
+++ b/docs/sources/flow/reference/components/module.git.md
@@ -6,8 +6,6 @@ aliases:
 - /docs/grafana-cloud/send-data/agent/flow/reference/components/module.git/
 canonical: https://grafana.com/docs/agent/latest/flow/reference/components/module.git/
 description: Learn about module.git
-labels:
-  stage: beta
 title: module.git
 ---
 
diff --git a/docs/sources/flow/reference/components/module.http.md b/docs/sources/flow/reference/components/module.http.md
index fde6e883ac56..35d928c21a46 100644
--- a/docs/sources/flow/reference/components/module.http.md
+++ b/docs/sources/flow/reference/components/module.http.md
@@ -6,8 +6,6 @@ aliases:
 - /docs/grafana-cloud/send-data/agent/flow/reference/components/module.http/
 canonical: https://grafana.com/docs/agent/latest/flow/reference/components/module.http/
 description: Learn about module.http
-labels:
-  stage: beta
 title: module.http
 ---
 
diff --git a/docs/sources/flow/reference/components/module.string.md b/docs/sources/flow/reference/components/module.string.md
index 62198d6ec2b8..887d38faf384 100644
--- a/docs/sources/flow/reference/components/module.string.md
+++ b/docs/sources/flow/reference/components/module.string.md
@@ -6,8 +6,6 @@ aliases:
 - /docs/grafana-cloud/send-data/agent/flow/reference/components/module.string/
 canonical: https://grafana.com/docs/agent/latest/flow/reference/components/module.string/
 description: Learn about module.string
-labels:
-  stage: beta
 title: module.string
 ---
 
diff --git a/docs/sources/flow/reference/components/otelcol.exporter.loadbalancing.md b/docs/sources/flow/reference/components/otelcol.exporter.loadbalancing.md
index f25e28bfa345..36537e93ac26 100644
--- a/docs/sources/flow/reference/components/otelcol.exporter.loadbalancing.md
+++ b/docs/sources/flow/reference/components/otelcol.exporter.loadbalancing.md
@@ -6,8 +6,6 @@ aliases:
 - /docs/grafana-cloud/send-data/agent/flow/reference/components/otelcol.exporter.loadbalancing/
 canonical: https://grafana.com/docs/agent/latest/flow/reference/components/otelcol.exporter.loadbalancing/
 description: Learn about otelcol.exporter.loadbalancing
-labels:
-  stage: beta
 title: otelcol.exporter.loadbalancing
 ---
 
@@ -18,7 +16,7 @@ title: otelcol.exporter.loadbalancing
 <!-- Include a picture of the LB architecture? -->
 
 `otelcol.exporter.loadbalancing` accepts logs and traces from other `otelcol` components
-and writes them over the network using the OpenTelemetry Protocol (OTLP) protocol. 
+and writes them over the network using the OpenTelemetry Protocol (OTLP) protocol.
 
 > **NOTE**: `otelcol.exporter.loadbalancing` is a wrapper over the upstream
 > OpenTelemetry Collector `loadbalancing` exporter. Bug reports or feature requests will
@@ -27,15 +25,15 @@ and writes them over the network using the OpenTelemetry Protocol (OTLP) protoco
 Multiple `otelcol.exporter.loadbalancing` components can be specified by giving them
 different labels.
 
-The decision which backend to use depends on the trace ID or the service name. 
-The backend load doesn't influence the choice. Even though this load-balancer won't do 
-round-robin balancing of the batches, the load distribution should be very similar among backends, 
+The decision which backend to use depends on the trace ID or the service name.
+The backend load doesn't influence the choice. Even though this load-balancer won't do
+round-robin balancing of the batches, the load distribution should be very similar among backends,
 with a standard deviation under 5% at the current configuration.
 
 `otelcol.exporter.loadbalancing` is especially useful for backends configured with tail-based samplers
 which choose a backend based on the view of the full trace.
 
-When a list of backends is updated, some of the signals will be rerouted to different backends. 
+When a list of backends is updated, some of the signals will be rerouted to different backends.
 Around R/N of the "routes" will be rerouted differently, where:
 
 * A "route" is either a trace ID or a service name mapped to a certain backend.
@@ -69,7 +67,7 @@ Name | Type | Description | Default | Required
 
 The `routing_key` attribute determines how to route signals across endpoints. Its value could be one of the following:
 * `"service"`: spans with the same `service.name` will be exported to the same backend.
-This is useful when using processors like the span metrics, so all spans for each service are sent to consistent Agent instances 
+This is useful when using processors like the span metrics, so all spans for each service are sent to consistent Agent instances
 for metric collection. Otherwise, metrics for the same services would be sent to different Agents, making aggregations inaccurate.
 * `"traceID"`: spans belonging to the same traceID will be exported to the same backend.
 
@@ -113,7 +111,7 @@ refers to a `static` block defined inside a `resolver` block.
 
 The `resolver` block configures how to retrieve the endpoint to which this exporter will send data.
 
-Inside the `resolver` block, either the [dns][] block or the [static][] block 
+Inside the `resolver` block, either the [dns][] block or the [static][] block
 should be specified. If both `dns` and `static` are specified, `dns` takes precedence.
 
 ### static block
@@ -128,8 +126,8 @@ Name | Type | Description | Default | Required
 
 ### dns block
 
-The `dns` block periodically resolves an IP address via the DNS `hostname` attribute. This IP address 
-and the port specified via the `port` attribute will then be used by the gRPC exporter 
+The `dns` block periodically resolves an IP address via the DNS `hostname` attribute. This IP address
+and the port specified via the `port` attribute will then be used by the gRPC exporter
 as the endpoint to which to export data to.
 
 The following arguments are supported:
@@ -143,8 +141,8 @@ Name | Type | Description | Default | Required
 
 ### kubernetes block
 
-You can use the `kubernetes` block to load balance across the pods of a Kubernetes service. 
-The Kubernetes API notifies {{< param "PRODUCT_NAME" >}} whenever a new pod is added or removed from the service. 
+You can use the `kubernetes` block to load balance across the pods of a Kubernetes service.
+The Kubernetes API notifies {{< param "PRODUCT_NAME" >}} whenever a new pod is added or removed from the service.
 The `kubernetes` resolver has a much faster response time than the `dns` resolver because it doesn't require polling.
 
 The following arguments are supported:
@@ -154,10 +152,10 @@ Name | Type | Description | Default | Required
 `service` | `string`       | Kubernetes service to resolve. |  | yes
 `ports`   | `list(number)` | Ports to use with the IP addresses resolved from `service`. | `[4317]` | no
 
-If no namespace is specified inside `service`, an attempt will be made to infer the namespace for this Agent. 
+If no namespace is specified inside `service`, an attempt will be made to infer the namespace for this Agent.
 If this fails, the `default` namespace will be used.
 
-Each of the ports listed in `ports` will be used with each of the IPs resolved from `service`. 
+Each of the ports listed in `ports` will be used with each of the IPs resolved from `service`.
 
 The "get", "list", and "watch" [roles](https://kubernetes.io/docs/reference/access-authn-authz/rbac/#role-example)
 must be granted in Kubernetes for the resolver to work.
@@ -173,7 +171,7 @@ The `otlp` block configures OTLP-related settings for exporting.
 
 ### client block
 
-The `client` block configures the gRPC client used by the component. 
+The `client` block configures the gRPC client used by the component.
 The endpoints used by the client block are the ones from the `resolver` block
 
 The following arguments are supported:
@@ -283,7 +281,7 @@ All spans for a given trace ID must go to the same tail sampling {{< param "PROD
 * This can be done by configuring `otelcol.exporter.loadbalancing` with `routing_key = "traceID"`.
 * If you do not configure `routing_key = "traceID"`, the sampling decision may be incorrect.
   The tail sampler must have a full view of the trace when making a sampling decision.
-  For example, a `rate_limiting` tail sampling strategy may incorrectly pass through 
+  For example, a `rate_limiting` tail sampling strategy may incorrectly pass through
   more spans than expected if the spans for the same trace are spread out to more than
   one {{< param "PRODUCT_NAME" >}} instance.
 
@@ -295,7 +293,7 @@ All spans for a given `service.name` must go to the same spanmetrics {{< param "
 * If you do not configure `routing_key = "service"`, metrics generated from spans might be incorrect.
 For example, if similar spans for the same `service.name` end up on different {{< param "PRODUCT_ROOT_NAME" >}} instances, the two {{< param "PRODUCT_ROOT_NAME" >}}s will have identical metric series for calculating span latency, errors, and number of requests.
 When both {{< param "PRODUCT_ROOT_NAME" >}} instances attempt to write the metrics to a database such as Mimir, the series may clash with each other.
-At best, this will lead to an error in {{< param "PRODUCT_ROOT_NAME" >}} and a rejected write to the metrics database. 
+At best, this will lead to an error in {{< param "PRODUCT_ROOT_NAME" >}} and a rejected write to the metrics database.
 At worst, it could lead to inaccurate data due to overlapping samples for the metric series.
 
 However, there are ways to scale `otelcol.connector.spanmetrics` without the need for a load balancer:
@@ -321,7 +319,7 @@ You could differentiate the series by adding an attribute such as `"collector.id
 The series from different {{< param "PRODUCT_ROOT_NAME" >}}s can be aggregated using PromQL queries on the backed metrics database.
 If the metrics are stored in Grafana Mimir, cardinality issues due to `"collector.id"` labels can be solved using [Adaptive Metrics][adaptive-metrics].
 
-A simpler, more scalable alternative to generating service graph metrics in {{< param "PRODUCT_ROOT_NAME" >}} is to generate them entirely in the backend database. 
+A simpler, more scalable alternative to generating service graph metrics in {{< param "PRODUCT_ROOT_NAME" >}} is to generate them entirely in the backend database.
 For example, service graphs can be [generated][tempo-servicegraphs] in Grafana Cloud by the Tempo traces database.
 
 [tempo-servicegraphs]: https://grafana.com/docs/tempo/latest/metrics-generator/service_graphs/
@@ -340,7 +338,7 @@ Unfortunately, this can also lead to side effects.
 For example, if `otelcol.connector.spanmetrics` is configured to generate exemplars, the tail sampling {{< param "PRODUCT_ROOT_NAME" >}}s might drop the trace that the exemplar points to.
 There is no coordination between the tail sampling {{< param "PRODUCT_ROOT_NAME" >}}s and the span metrics {{< param "PRODUCT_ROOT_NAME" >}}s to make sure trace IDs for exemplars are kept.
 
-<!-- 
+<!--
 TODO: Add a troubleshooting section?
 1. Use GODEBUG for DNS resolver logging
 2. Enable debug logging on the Agent
@@ -361,7 +359,7 @@ information.
 
 ### Static resolver
 
-This example accepts OTLP logs and traces over gRPC. It then sends them in a load-balanced 
+This example accepts OTLP logs and traces over gRPC. It then sends them in a load-balanced
 way to "localhost:55690" or "localhost:55700".
 
 ```river
@@ -389,7 +387,7 @@ otelcol.exporter.loadbalancing "default" {
 
 ### DNS resolver
 
-When configured with a `dns` resolver, `otelcol.exporter.loadbalancing` will do a DNS lookup 
+When configured with a `dns` resolver, `otelcol.exporter.loadbalancing` will do a DNS lookup
 on regular intervals. Spans are exported to the addresses the DNS lookup returned.
 
 ```river
@@ -658,7 +656,7 @@ k3d cluster delete grafana-agent-lb-test
 
 ### Kubernetes resolver
 
-When you configure `otelcol.exporter.loadbalancing`  with a `kubernetes` resolver, the Kubernetes API notifies {{< param "PRODUCT_NAME" >}} whenever a new pod is added or removed from the service. 
+When you configure `otelcol.exporter.loadbalancing`  with a `kubernetes` resolver, the Kubernetes API notifies {{< param "PRODUCT_NAME" >}} whenever a new pod is added or removed from the service.
 Spans are exported to the addresses from the Kubernetes API, combined with all the possible `ports`.
 
 ```river
@@ -681,7 +679,7 @@ The following example shows a Kubernetes configuration that sets up two sets of
 * A pool of load-balancer {{< param "PRODUCT_ROOT_NAME" >}}s:
   * Spans are received from instrumented applications via `otelcol.receiver.otlp`
   * Spans are exported via `otelcol.exporter.loadbalancing`.
-  * The load-balancer {{< param "PRODUCT_ROOT_NAME" >}}s will get notified by the Kubernetes API any time a pod 
+  * The load-balancer {{< param "PRODUCT_ROOT_NAME" >}}s will get notified by the Kubernetes API any time a pod
     is added or removed from the pool of sampling {{< param "PRODUCT_ROOT_NAME" >}}s.
 * A pool of sampling {{< param "PRODUCT_ROOT_NAME" >}}s:
   * The sampling {{< param "PRODUCT_ROOT_NAME" >}}s do not need to run behind a headless service.
diff --git a/docs/sources/flow/reference/components/otelcol.processor.resourcedetection.md b/docs/sources/flow/reference/components/otelcol.processor.resourcedetection.md
index 9f4f5d882e68..5b708f5452fd 100644
--- a/docs/sources/flow/reference/components/otelcol.processor.resourcedetection.md
+++ b/docs/sources/flow/reference/components/otelcol.processor.resourcedetection.md
@@ -5,8 +5,6 @@ aliases:
 - /docs/grafana-cloud/monitor-infrastructure/integrations/agent/flow/reference/components/otelcol.processor.resourcedetection/
 - /docs/grafana-cloud/send-data/agent/flow/reference/components/otelcol.processor.resourcedetection/
 canonical: https://grafana.com/docs/agent/latest/flow/reference/components/otelcol.processor.resourcedetection/
-labels:
-  stage: beta
 title: otelcol.processor.resourcedetection
 description: Learn about otelcol.processor.resourcedetection
 ---
@@ -366,7 +364,7 @@ Example values:
 * `cloud.provider`: `"azure"`
 * `cloud.platform`: `"azure_vm"`
 
-Azure AKS cluster name is derived from the Azure Instance Metadata Service's (IMDS) infrastructure resource group field. 
+Azure AKS cluster name is derived from the Azure Instance Metadata Service's (IMDS) infrastructure resource group field.
 This field contains the resource group and name of the cluster, separated by underscores. For example: `MC_<resource group>_<cluster name>_<location>`.
 
 Example:
@@ -377,7 +375,7 @@ Example:
 
 The cluster name is detected if it does not contain underscores and if a custom infrastructure resource group name was not used.
 
-If accurate parsing cannot be performed, the infrastructure resource group value is returned. 
+If accurate parsing cannot be performed, the infrastructure resource group value is returned.
 This value can be used to uniquely identify the cluster, because Azure will not allow users to create multiple clusters with the same infrastructure resource group name.
 
 ### consul
diff --git a/docs/sources/flow/reference/components/otelcol.processor.tail_sampling.md b/docs/sources/flow/reference/components/otelcol.processor.tail_sampling.md
index baeb5593db53..d9af10a8f8ab 100644
--- a/docs/sources/flow/reference/components/otelcol.processor.tail_sampling.md
+++ b/docs/sources/flow/reference/components/otelcol.processor.tail_sampling.md
@@ -6,8 +6,6 @@ aliases:
 - /docs/grafana-cloud/send-data/agent/flow/reference/components/otelcol.processor.tail_sampling/
 canonical: https://grafana.com/docs/agent/latest/flow/reference/components/otelcol.processor.tail_sampling/
 description: Learn about otelcol.processor.tail_sampling
-labels:
-  stage: beta
 title: otelcol.processor.tail_sampling
 ---
 
@@ -241,7 +239,7 @@ Set `max_spans` to `0`, if you do not want to limit the policy samples based on
 
 ### boolean_attribute block
 
-The `boolean_attribute` block configures a policy of type `boolean_attribute`. 
+The `boolean_attribute` block configures a policy of type `boolean_attribute`.
 The policy samples based on a boolean attribute (resource and record).
 
 The following arguments are supported:
@@ -253,7 +251,7 @@ Name | Type | Description | Default | Required
 
 ### ottl_condition block
 
-The `ottl_condition` block configures a policy of type `ottl_condition`. The policy samples based on a given boolean 
+The `ottl_condition` block configures a policy of type `ottl_condition`. The policy samples based on a given boolean
 [OTTL](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/pkg/ottl) condition (span and span event).
 
 The following arguments are supported:
diff --git a/docs/sources/flow/reference/components/otelcol.receiver.loki.md b/docs/sources/flow/reference/components/otelcol.receiver.loki.md
index a658f35a7fee..b6e9a6c63d8c 100644
--- a/docs/sources/flow/reference/components/otelcol.receiver.loki.md
+++ b/docs/sources/flow/reference/components/otelcol.receiver.loki.md
@@ -6,8 +6,6 @@ aliases:
 - /docs/grafana-cloud/send-data/agent/flow/reference/components/otelcol.receiver.loki/
 canonical: https://grafana.com/docs/agent/latest/flow/reference/components/otelcol.receiver.loki/
 description: Learn about otelcol.receiver.loki
-labels:
-  stage: beta
 title: otelcol.receiver.loki
 ---
 
diff --git a/docs/sources/flow/reference/components/otelcol.receiver.prometheus.md b/docs/sources/flow/reference/components/otelcol.receiver.prometheus.md
index ce9e9b9f897b..fad0eea9d6c8 100644
--- a/docs/sources/flow/reference/components/otelcol.receiver.prometheus.md
+++ b/docs/sources/flow/reference/components/otelcol.receiver.prometheus.md
@@ -6,8 +6,6 @@ aliases:
 - /docs/grafana-cloud/send-data/agent/flow/reference/components/otelcol.receiver.prometheus/
 canonical: https://grafana.com/docs/agent/latest/flow/reference/components/otelcol.receiver.prometheus/
 description: Learn about otelcol.receiver.prometheus
-labels:
-  stage: beta
 title: otelcol.receiver.prometheus
 ---
 
diff --git a/docs/sources/flow/reference/components/prometheus.exporter.postgres.md b/docs/sources/flow/reference/components/prometheus.exporter.postgres.md
index 5778217cfa95..819dabe4893c 100644
--- a/docs/sources/flow/reference/components/prometheus.exporter.postgres.md
+++ b/docs/sources/flow/reference/components/prometheus.exporter.postgres.md
@@ -6,8 +6,6 @@ aliases:
 - /docs/grafana-cloud/send-data/agent/flow/reference/components/prometheus.exporter.postgres/
 canonical: https://grafana.com/docs/agent/latest/flow/reference/components/prometheus.exporter.postgres/
 description: Learn about prometheus.exporter.postgres
-labels:
-  stage: beta
 title: prometheus.exporter.postgres
 ---
 
diff --git a/docs/sources/flow/reference/components/prometheus.exporter.windows.md b/docs/sources/flow/reference/components/prometheus.exporter.windows.md
index db53b6e02f90..a38befddde21 100644
--- a/docs/sources/flow/reference/components/prometheus.exporter.windows.md
+++ b/docs/sources/flow/reference/components/prometheus.exporter.windows.md
@@ -66,15 +66,15 @@ text_file      | [text_file][]      | Configures the text_file collector.      |
 [dfsr]: #dfsr-block
 [exchange]: #exchange-block
 [iis]: #iis-block
-[logical_disk]: #logical_disk-block
+[logical_disk]: #logicaldisk-block
 [msmq]: #msmq-block
 [mssql]: #mssql-block
 [network]: #network-block
 [process]: #process-block
-[scheduled_task]: #scheduled_task-block
+[scheduled_task]: #scheduledtask-block
 [service]: #service-block
 [smtp]: #smtp-block
-[text_file]: #text_file-block
+[text_file]: #textfile-block
 
 ### dfsr block
 
@@ -263,14 +263,14 @@ Name     | Description | Enabled by default
 [mscluster_resourcegroup](https://github.com/prometheus-community/windows_exporter/blob/master/docs/collector.mscluster_resourcegroup.md) | MSCluster ResourceGroup metrics |
 [msmq](https://github.com/prometheus-community/windows_exporter/blob/master/docs/collector.msmq.md) | MSMQ queues |
 [mssql](https://github.com/prometheus-community/windows_exporter/blob/master/docs/collector.mssql.md) | [SQL Server Performance Objects](https://docs.microsoft.com/en-us/sql/relational-databases/performance-monitor/use-sql-server-objects#SQLServerPOs) metrics  |
-[netframework_clrexceptions](https://github.com/prometheus-community/windows_exporter/blob/master/docs/collector.netframework.md#clr-exceptions) | .NET Framework CLR Exceptions |
-[netframework_clrinterop](https://github.com/prometheus-community/windows_exporter/blob/master/docs/collector.netframework.md#clr-interop) | .NET Framework Interop Metrics |
-[netframework_clrjit](https://github.com/prometheus-community/windows_exporter/blob/master/docs/collector.netframework.md#clr-jit) | .NET Framework JIT metrics |
-[netframework_clrloading](https://github.com/prometheus-community/windows_exporter/blob/master/docs/collector.netframework.md#clr-loading) | .NET Framework CLR Loading metrics |
-[netframework_clrlocksandthreads](https://github.com/prometheus-community/windows_exporter/blob/master/docs/collector.netframework.md#clr-locks-and-threads) | .NET Framework locks and metrics threads |
-[netframework_clrmemory](https://github.com/prometheus-community/windows_exporter/blob/master/docs/collector.netframework.md#clr-memory) |  .NET Framework Memory metrics |
-[netframework_clrremoting](https://github.com/prometheus-community/windows_exporter/blob/master/docs/collector.netframework.md#clr-remoting) | .NET Framework Remoting metrics |
-[netframework_clrsecurity](https://github.com/prometheus-community/windows_exporter/blob/master/docs/collector.netframework.md#clr-security) | .NET Framework Security Check metrics |
+[netframework_clrexceptions](https://github.com/prometheus-community/windows_exporter/blob/master/docs/collector.netframework_clrexceptions.md) | .NET Framework CLR Exceptions |
+[netframework_clrinterop](https://github.com/prometheus-community/windows_exporter/blob/master/docs/collector.netframework_clrinterop.md) | .NET Framework Interop Metrics |
+[netframework_clrjit](https://github.com/prometheus-community/windows_exporter/blob/master/docs/collector.netframework_clrjit.md) | .NET Framework JIT metrics |
+[netframework_clrloading](https://github.com/prometheus-community/windows_exporter/blob/master/docs/collector.netframework_clrloading.md) | .NET Framework CLR Loading metrics |
+[netframework_clrlocksandthreads](https://github.com/prometheus-community/windows_exporter/blob/master/docs/collector.netframework_clrlocksandthreads.md) | .NET Framework locks and metrics threads |
+[netframework_clrmemory](https://github.com/prometheus-community/windows_exporter/blob/master/docs/collector.netframework_clrmemory.md) |  .NET Framework Memory metrics |
+[netframework_clrremoting](https://github.com/prometheus-community/windows_exporter/blob/master/docs/collector.netframework_clrremoting.md) | .NET Framework Remoting metrics |
+[netframework_clrsecurity](https://github.com/prometheus-community/windows_exporter/blob/master/docs/collector.netframework_clrsecurity.md) | .NET Framework Security Check metrics |
 [net](https://github.com/prometheus-community/windows_exporter/blob/master/docs/collector.net.md) | Network interface I/O | &#10003;
 [os](https://github.com/prometheus-community/windows_exporter/blob/master/docs/collector.os.md) | OS metrics (memory, processes, users) | &#10003;
 [physical_disk](https://github.com/prometheus-community/windows_exporter/blob/master/docs/collector.physical_disk.md) | Physical disks | &#10003;
diff --git a/docs/sources/flow/reference/components/prometheus.operator.podmonitors.md b/docs/sources/flow/reference/components/prometheus.operator.podmonitors.md
index 34d73ae78477..125946422a9d 100644
--- a/docs/sources/flow/reference/components/prometheus.operator.podmonitors.md
+++ b/docs/sources/flow/reference/components/prometheus.operator.podmonitors.md
@@ -6,8 +6,6 @@ aliases:
 - /docs/grafana-cloud/send-data/agent/flow/reference/components/prometheus.operator.podmonitors/
 canonical: https://grafana.com/docs/agent/latest/flow/reference/components/prometheus.operator.podmonitors/
 description: Learn about prometheus.operator.podmonitors
-labels:
-  stage: beta
 title: prometheus.operator.podmonitors
 ---
 
diff --git a/docs/sources/flow/reference/components/prometheus.operator.probes.md b/docs/sources/flow/reference/components/prometheus.operator.probes.md
index 01ca2fd73017..984d82a234e6 100644
--- a/docs/sources/flow/reference/components/prometheus.operator.probes.md
+++ b/docs/sources/flow/reference/components/prometheus.operator.probes.md
@@ -6,8 +6,6 @@ aliases:
 - /docs/grafana-cloud/send-data/agent/flow/reference/components/prometheus.operator.probes/
 canonical: https://grafana.com/docs/agent/latest/flow/reference/components/prometheus.operator.probes/
 description: Learn about prometheus.operator.probes
-labels:
-  stage: beta
 title: prometheus.operator.probes
 ---
 
diff --git a/docs/sources/flow/reference/components/prometheus.operator.servicemonitors.md b/docs/sources/flow/reference/components/prometheus.operator.servicemonitors.md
index 24a1b886aa30..0f62760271ed 100644
--- a/docs/sources/flow/reference/components/prometheus.operator.servicemonitors.md
+++ b/docs/sources/flow/reference/components/prometheus.operator.servicemonitors.md
@@ -6,8 +6,6 @@ aliases:
 - /docs/grafana-cloud/send-data/agent/flow/reference/components/prometheus.operator.servicemonitors/
 canonical: https://grafana.com/docs/agent/latest/flow/reference/components/prometheus.operator.servicemonitors/
 description: Learn about prometheus.operator.servicemonitors
-labels:
-  stage: beta
 title: prometheus.operator.servicemonitors
 ---
 
diff --git a/docs/sources/flow/reference/components/pyroscope.ebpf.md b/docs/sources/flow/reference/components/pyroscope.ebpf.md
index 04e257cac338..ec1267c75f66 100644
--- a/docs/sources/flow/reference/components/pyroscope.ebpf.md
+++ b/docs/sources/flow/reference/components/pyroscope.ebpf.md
@@ -6,8 +6,6 @@ aliases:
 - /docs/grafana-cloud/send-data/agent/flow/reference/components/pyroscope.ebpf/
 canonical: https://grafana.com/docs/agent/latest/flow/reference/components/pyroscope.ebpf/
 description: Learn about pyroscope.ebpf
-labels:
-  stage: beta
 title: pyroscope.ebpf
 ---
 
@@ -97,7 +95,7 @@ can help you pin down a profiling target.
 | `__name__`         | pyroscope metric name. Defaults to `process_cpu`.                                                                                |
 | `__container_id__` | The container ID derived from target.                                                                                            |
 
-### Targets 
+### Targets
 
 One of the following special labels _must_ be included in each target of `targets` and the label must correspond to the container or process that is profiled:
 
@@ -106,7 +104,7 @@ One of the following special labels _must_ be included in each target of `target
 * `__meta_kubernetes_pod_container_id`: The ID of the Kubernetes pod container.
 * `__process_pid__` : The process ID.
 
-Each process is then associated with a specified target from the targets list, determined by a container ID or process PID. 
+Each process is then associated with a specified target from the targets list, determined by a container ID or process PID.
 
 If a process's container ID matches a target's container ID label, the stack traces are aggregated per target based on the container ID.
 If a process's PID matches a target's process PID label, the stack traces are aggregated per target based on the process PID.
@@ -289,7 +287,7 @@ pyroscope.write "staging" {
   }
 }
 
-pyroscope.ebpf "default" {  
+pyroscope.ebpf "default" {
   forward_to   = [ pyroscope.write.staging.receiver ]
   targets      = discovery.relabel.local_containers.output
 }
diff --git a/docs/sources/flow/reference/components/pyroscope.scrape.md b/docs/sources/flow/reference/components/pyroscope.scrape.md
index 9d00df3a8c3b..4278c9f093ac 100644
--- a/docs/sources/flow/reference/components/pyroscope.scrape.md
+++ b/docs/sources/flow/reference/components/pyroscope.scrape.md
@@ -6,8 +6,6 @@ aliases:
 - /docs/grafana-cloud/send-data/agent/flow/reference/components/pyroscope.scrape/
 canonical: https://grafana.com/docs/agent/latest/flow/reference/components/pyroscope.scrape/
 description: Learn about pyroscope.scrape
-labels:
-  stage: beta
 title: pyroscope.scrape
 ---
 
@@ -15,15 +13,15 @@ title: pyroscope.scrape
 
 {{< docs/shared lookup="flow/stability/beta.md" source="agent" version="<AGENT_VERSION>" >}}
 
-`pyroscope.scrape` collects [pprof] performance profiles for a given set of HTTP `targets`. 
+`pyroscope.scrape` collects [pprof] performance profiles for a given set of HTTP `targets`.
 
 `pyroscope.scrape` mimcks the scraping behavior of `prometheus.scrape`.
 Similarly to how Prometheus scrapes metrics via HTTP, `pyroscope.scrape` collects profiles via HTTP requests.
 
-Unlike Prometheus, which usually only scrapes one `/metrics` endpoint per target, 
+Unlike Prometheus, which usually only scrapes one `/metrics` endpoint per target,
 `pyroscope.scrape` may need to scrape multiple endpoints for the same target.
-This is because different types of profiles are scraped on different endpoints. 
-For example, "mutex" profiles may be scraped on a `/debug/pprof/delta_mutex` HTTP endpoint, whereas 
+This is because different types of profiles are scraped on different endpoints.
+For example, "mutex" profiles may be scraped on a `/debug/pprof/delta_mutex` HTTP endpoint, whereas
 memory consumption may be scraped on a `/debug/pprof/allocs` HTTP endpoint.
 
 The profile paths, protocol scheme, scrape interval, scrape timeout,
@@ -37,7 +35,7 @@ If a scrape request fails, the [debug UI][] for `pyroscope.scrape` will show:
 * The time of the last successful scrape.
 * The labels last used for scraping.
 
-The scraped performance profiles can be forwarded to components such as 
+The scraped performance profiles can be forwarded to components such as
 `pyroscope.write` via the `forward_to` argument.
 
 Multiple `pyroscope.scrape` components can be specified by giving them different labels.
@@ -55,7 +53,7 @@ pyroscope.scrape "LABEL" {
 
 ## Arguments
 
-`pyroscope.scrape` starts a new scrape job to scrape all of the input targets. 
+`pyroscope.scrape` starts a new scrape job to scrape all of the input targets.
 Multiple scrape jobs can be started for a single input target
 when scraping multiple profile types.
 
@@ -63,7 +61,7 @@ The list of arguments that can be used to configure the block is
 presented below.
 
 Any omitted arguments take on their default values. If conflicting
-arguments are being passed (for example, configuring both `bearer_token` 
+arguments are being passed (for example, configuring both `bearer_token`
 and `bearer_token_file`), then `pyroscope.scrape` will fail to start and will report an error.
 
 The following arguments are supported:
@@ -105,7 +103,7 @@ For example, the `job_name` of `pyroscope.scrape "local" { ... }` will be `"pyro
 
 #### `targets` argument
 
-The list of `targets` can be provided [statically][example_static_targets], [dynamically][example_dynamic_targets], 
+The list of `targets` can be provided [statically][example_static_targets], [dynamically][example_dynamic_targets],
 or a [combination of both][example_static_and_dynamic_targets].
 
 The special `__address__` label _must always_ be present and corresponds to the
@@ -113,9 +111,9 @@ The special `__address__` label _must always_ be present and corresponds to the
 
 Labels starting with a double underscore (`__`) are treated as _internal_, and are removed prior to scraping.
 
-The special label `service_name` is required and must always be present. 
-If it is not specified, `pyroscope.scrape` will attempt to infer it from 
-either of the following sources, in this order: 
+The special label `service_name` is required and must always be present.
+If it is not specified, `pyroscope.scrape` will attempt to infer it from
+either of the following sources, in this order:
 1. `__meta_kubernetes_pod_annotation_pyroscope_io_service_name` which is a `pyroscope.io/service_name` pod annotation.
 2. `__meta_kubernetes_namespace` and `__meta_kubernetes_pod_container_name`
 3. `__meta_docker_container_name`
@@ -123,7 +121,7 @@ either of the following sources, in this order:
 
 If `service_name` is not specified and could not be inferred, then it is set to `unspecified`.
 
-The following labels are automatically injected to the scraped profiles 
+The following labels are automatically injected to the scraped profiles
 so that they can be linked to a scrape target:
 
 | Label            | Description                                                      |
@@ -134,8 +132,8 @@ so that they can be linked to a scrape target:
 
 #### `scrape_interval` argument
 
-The `scrape_interval` typically refers to the frequency with which {{< param "PRODUCT_NAME" >}} collects performance profiles from the monitored targets. 
-It represents the time interval between consecutive scrapes or data collection events. 
+The `scrape_interval` typically refers to the frequency with which {{< param "PRODUCT_NAME" >}} collects performance profiles from the monitored targets.
+It represents the time interval between consecutive scrapes or data collection events.
 This parameter is important for controlling the trade-off between resource usage and the freshness of the collected data.
 
 If `scrape_interval` is short:
@@ -150,16 +148,16 @@ If `scrape_interval` is long:
   * Lower resource consumption.
 * Disadvantages:
   * More profiles may be lost if the application being scraped crashes.
-  * If the [delta argument][] is set to `true`, the batch size of 
+  * If the [delta argument][] is set to `true`, the batch size of
     each remote write to Pyroscope may be bigger.
     The Pyroscope database may need to be tuned with higher limits.
-  * If the [delta argument][] is set to `true`, there is a larger risk of 
+  * If the [delta argument][] is set to `true`, there is a larger risk of
     reaching the HTTP server timeouts of the application being scraped.
 
 For example, consider this situation:
 * `pyroscope.scrape` is configured with a `scrape_interval` of `"60s"`.
 * The application being scraped is running an HTTP server with a timeout of 30 seconds.
-* Any scrape HTTP requests where the [delta argument][] is set to `true` will fail, 
+* Any scrape HTTP requests where the [delta argument][] is set to `true` will fail,
   because they will attempt to run for 59 seconds.
 
 ## Blocks
@@ -190,8 +188,8 @@ The `>` symbol indicates deeper levels of nesting. For example,
 `oauth2 > tls_config` refers to a `tls_config` block defined inside
 an `oauth2` block.
 
-Any omitted blocks take on their default values. For example, 
-if `profile.mutex` is not specified in the config, 
+Any omitted blocks take on their default values. For example,
+if `profile.mutex` is not specified in the config,
 the defaults documented in [profile.mutex][] will be used.
 
 [basic_auth]: #basic_auth-block
@@ -450,7 +448,7 @@ scrape job on the component's debug endpoint.
 
 ### Default endpoints of static targets
 
-The following example sets up a scrape job of a statically configured 
+The following example sets up a scrape job of a statically configured
 list of targets - {{< param "PRODUCT_ROOT_NAME" >}} itself and Pyroscope.
 The scraped profiles are sent to `pyroscope.write` which remote writes them to a Pyroscope database.
 
@@ -489,7 +487,7 @@ http://localhost:12345/debug/pprof/profile?seconds=14
 
 Note that `seconds=14` is added to the `/debug/pprof/profile` endpoint, because:
 * The `delta` argument of the `profile.process_cpu` block is `true` by default.
-* `scrape_interval` is `"15s"` by default. 
+* `scrape_interval` is `"15s"` by default.
 
 Also note that the `/debug/fgprof` endpoint will not be scraped, because
 the `enabled` argument of the `profile.fgprof` block is `false` by default.
diff --git a/docs/sources/flow/reference/components/pyroscope.write.md b/docs/sources/flow/reference/components/pyroscope.write.md
index 403aef0719e0..6e5966a31f40 100644
--- a/docs/sources/flow/reference/components/pyroscope.write.md
+++ b/docs/sources/flow/reference/components/pyroscope.write.md
@@ -6,8 +6,6 @@ aliases:
 - /docs/grafana-cloud/send-data/agent/flow/reference/components/pyroscope.write/
 canonical: https://grafana.com/docs/agent/latest/flow/reference/components/pyroscope.write/
 description: Learn about pyroscope.write
-labels:
-  stage: beta
 title: pyroscope.write
 ---
 
diff --git a/docs/sources/flow/reference/config-blocks/import.file.md b/docs/sources/flow/reference/config-blocks/import.file.md
index 63befc6e2007..47ab40bb2913 100644
--- a/docs/sources/flow/reference/config-blocks/import.file.md
+++ b/docs/sources/flow/reference/config-blocks/import.file.md
@@ -6,8 +6,6 @@ aliases:
   - /docs/grafana-cloud/send-data/agent/flow/reference/config-blocks/import.file/
 canonical: https://grafana.com/docs/agent/latest/flow/reference/config-blocks/import.file/
 description: Learn about the import.file configuration block
-labels:
-  stage: beta
 title: import.file
 refs:
   module:
diff --git a/docs/sources/flow/tasks/configure-agent-clustering.md b/docs/sources/flow/tasks/configure-agent-clustering.md
index 2943e77e32b4..89ab83d8329e 100644
--- a/docs/sources/flow/tasks/configure-agent-clustering.md
+++ b/docs/sources/flow/tasks/configure-agent-clustering.md
@@ -43,6 +43,9 @@ This topic describes how to add clustering to an existing installation.
 
 This section guides you through enabling clustering when {{< param "PRODUCT_NAME" >}} is installed on Kubernetes using the {{< param "PRODUCT_ROOT_NAME" >}} [Helm chart](ref:install-helm).
 
+### Before you begin
+
+- Ensure that your `values.yaml` file has `controller.type` set to `statefulset`.
 
 ### Steps