diff --git a/content/en/agent/fleet_automation/_index.md b/content/en/agent/fleet_automation/_index.md
index 2b012147b45..a183e5e8b9d 100644
--- a/content/en/agent/fleet_automation/_index.md
+++ b/content/en/agent/fleet_automation/_index.md
@@ -38,6 +38,7 @@ With Fleet Automation, you can:
 - **[Configure Datadog Agents][4]** to centralize setup and gain visibility into your environments faster.
 - **[Keep your fleet up to date][5]** by identifying and upgrading outdated Agent and OTel Collector versions.
 - **[Send a support flare remotely][6]**, reducing the time it takes to debug issues on an Agent or DDOT Collector.
+- **[View your fleet by Kubernetes cluster][7]** to inspect and configure Agents grouped by cluster instead of as individual hosts.
 
 ## Fleet Automation API
 
@@ -70,3 +71,4 @@ For information on setting up roles and permissions, see [Access Control][2].
 [4]: /agent/fleet_automation/configure_agents/
 [5]: /agent/fleet_automation/upgrade_agents/
 [6]: /agent/troubleshooting/send_a_flare/#send-a-flare-from-the-datadog-site
+[7]: /agent/fleet_automation/fleet_view/#kubernetes-view
diff --git a/content/en/agent/fleet_automation/fleet_view.md b/content/en/agent/fleet_automation/fleet_view.md
index 18f71c5550b..4d3a92df948 100644
--- a/content/en/agent/fleet_automation/fleet_view.md
+++ b/content/en/agent/fleet_automation/fleet_view.md
@@ -8,6 +8,9 @@ further_reading:
 - link: "/agent/troubleshooting/send_a_flare/"
   tag: "Documentation"
   text: "Send a flare"
+- link: "/containers/kubernetes/installation/"
+  tag: "Documentation"
+  text: "Install the Datadog Agent on Kubernetes"
 ---
 
 Use [Fleet View][1] to gain insight into observability gaps on your hosts, outdated Agents or OTel Collectors, and Agents with integration issues.
@@ -39,6 +42,13 @@ Select a Datadog Agent or OTel Collector to view its configuration, connected in
 
 {{< img src="agent/fleet_automation/fleet-automation-view-config.png" alt="The Agent detail panel showing configuration, connected integrations, and audit events." style="width:100%;" >}}
 
+## Search and filter
+
+Use the search bar at the top of Fleet View to find specific Agents, OTel Collectors, or clusters across your fleet. You can:
+
+- Perform free text search by hostname or cluster name
+- Filter by host and Agent tags, such as operating system, environment (`env`), team, and enabled products (`products_enabled`) <!-- confirm whether this is host-view only -->
+
 ## Visualize OTel pipelines
 
 The {{< ui >}}Configuration{{< /ui >}} tab for an OTel Collector includes {{< ui >}}Pipeline{{< /ui >}} and {{< ui >}}Topology{{< /ui >}} views. These views provide end-to-end visibility into how telemetry flows through your OTel pipelines.
@@ -88,6 +98,58 @@ When you contact Datadog Support with Remote Configuration enabled, the Support
 
 {{< img src="agent/fleet_automation/fleet_automation_remote_flare.png" alt="The support tab for an Agent with the Send Flare button." style="width:100%;" >}}
 
+## Kubernetes view
+
+You can also view Datadog Agents running in Kubernetes environments.
+
+By default, Fleet View lists infrastructure as individual hosts. Use the {{< ui >}}View by infra type{{< /ui >}} toggle to switch to [Kubernetes view][4], which shows Agents by Kubernetes cluster instead.
+
+Each row is a cluster managed by the [Datadog Operator][5] or Helm chart, and the Agents in it (Node Agents, Cluster Agent, Cluster Check Runners) appear grouped per cluster instead of as individual hosts.
+
+### Prerequisites for Kubernetes view
+
+To view clusters in Kubernetes view, you must be running one of the following:
+
+- [Datadog Operator][5] v1.22 or later
+- Datadog Helm chart v3.157.0 or later
+
+Some capabilities require specific versions:
+
+- To view DatadogAgent CRD configuration: Datadog Operator v1.24 or later
+- To configure the Datadog Operator from Fleet View: Datadog Operator v1.27 or later
+- To view integration details: Agent v7.72.0 or later (integrations list), or Agent v7.79.0 or later (with status report)
+
+You must also enable the following feature flags:
+
+```
+remoteUpdatesEnabled=true
+createControllerRevisions=true
+remoteConfiguration:
+  enabled: true
+```
+
+### View Kubernetes clusters
+
+Clusters are listed alphabetically by cluster name. The table lists each cluster's name, deployment method (Datadog Operator or Helm), namespace, Agent version, Agent pod status, readiness, age, and number of restarts.
+
+To find a specific cluster, you can [search](#search-and-filter) by cluster name. <!-- more? -->
+
+Click a cluster to view:
+
+- Cluster details, such as environment and tags
+- Cluster-level Agents (Cluster Agent and Cluster Check Runners)
+- Node Agents
+
+For clusters managed with the Datadog Operator v1.24 or later, the {{< ui >}}Configuration{{< /ui >}} tab shows the cluster's configuration data. With Datadog Operator v1.27 or later, you can also edit the configuration from this tab. (Clusters deployed with Helm do not have the configuration tab -- confirm)
+
+### Limitations
+
+Compared to host view, Kubernetes view has the following limitations:
+
+- You cannot send remote support flares.
+- There is no view for OpenTelemetry Collector configuration.
+- Fleet Automation API access is not available.
+
 ## Further Reading
 
 {{< partial name="whats-next/whats-next.html" >}}
@@ -95,3 +157,5 @@ When you contact Datadog Support with Remote Configuration enabled, the Support
 [1]: https://app.datadoghq.com/fleet
 [2]: /agent/troubleshooting/send_a_flare/#send-a-flare-from-the-datadog-site
 [3]: /agent/configuration/agent-configuration-files/
+[4]: https://app.datadoghq.com/fleet?view_by=clusters
+[5]: /containers/datadog_operator
\ No newline at end of file