diff --git a/docs/toolhive/guides-k8s/connect-clients.mdx b/docs/toolhive/guides-k8s/connect-clients.mdx
index f5473eb6..9f32ad8a 100644
--- a/docs/toolhive/guides-k8s/connect-clients.mdx
+++ b/docs/toolhive/guides-k8s/connect-clients.mdx
@@ -56,8 +56,6 @@ flowchart TB
   [Run MCP servers in Kubernetes](./run-mcp-k8s.mdx))
 - An Ingress controller or Gateway API implementation installed in your cluster
   (for external access)
-- [`kubectl`](https://kubernetes.io/docs/tasks/tools/) configured to communicate
-  with your cluster
 
 ## Connect from outside the cluster
 
diff --git a/docs/toolhive/guides-k8s/mcp-server-entry.mdx b/docs/toolhive/guides-k8s/mcp-server-entry.mdx
index 1cd6900f..3f7feead 100644
--- a/docs/toolhive/guides-k8s/mcp-server-entry.mdx
+++ b/docs/toolhive/guides-k8s/mcp-server-entry.mdx
@@ -38,13 +38,8 @@ and connects to them directly.
 
 ## Prerequisites
 
-- A Kubernetes cluster (current and two previous minor versions are supported)
-- Permissions to create resources in the cluster
-- [`kubectl`](https://kubernetes.io/docs/tasks/tools/) configured to communicate
-  with your cluster
-- The ToolHive operator installed in your cluster (see
-  [Deploy the operator](./deploy-operator.mdx))
-- A remote MCP server that supports HTTP transport (SSE or Streamable HTTP)
+You'll need a remote MCP server that supports HTTP transport (SSE or Streamable
+HTTP).
 
 ## When to use MCPServerEntry vs. MCPRemoteProxy
 
diff --git a/docs/toolhive/guides-k8s/remote-mcp-proxy.mdx b/docs/toolhive/guides-k8s/remote-mcp-proxy.mdx
index 9ce3f33a..16602e40 100644
--- a/docs/toolhive/guides-k8s/remote-mcp-proxy.mdx
+++ b/docs/toolhive/guides-k8s/remote-mcp-proxy.mdx
@@ -44,13 +44,7 @@ flowchart LR
 
 ## Prerequisites
 
-- A Kubernetes cluster (current and two previous minor versions are supported)
-- Permissions to create resources in the cluster
-- [`kubectl`](https://kubernetes.io/docs/tasks/tools/) configured to communicate
-  with your cluster
-- The ToolHive operator installed in your cluster (see
-  [Deploy the operator](./deploy-operator.mdx))
-- An OIDC identity provider (Keycloak, Okta, Azure AD, etc.)
+- An OIDC identity provider (Keycloak, Okta, Microsoft Entra ID, etc.)
 - Access to a remote MCP server that supports HTTP transport (SSE or Streamable
   HTTP)
 
diff --git a/docs/toolhive/guides-k8s/run-mcp-k8s.mdx b/docs/toolhive/guides-k8s/run-mcp-k8s.mdx
index 297f7c48..87eeb4e7 100644
--- a/docs/toolhive/guides-k8s/run-mcp-k8s.mdx
+++ b/docs/toolhive/guides-k8s/run-mcp-k8s.mdx
@@ -7,12 +7,8 @@ description:
 
 ## Prerequisites
 
-- A Kubernetes cluster (current and two previous minor versions are supported)
-- Permissions to create resources in the cluster
-- [`kubectl`](https://kubernetes.io/docs/tasks/tools/) configured to communicate
-  with your cluster
-- The ToolHive operator installed in your cluster (see
-  [Deploy the operator](./deploy-operator.mdx))
+You'll need a Kubernetes cluster with the ToolHive operator installed (see
+[Deploy the operator](./deploy-operator.mdx)).
 
 ## Overview