diff --git a/docs/toolhive/guides-k8s/auth-k8s.mdx b/docs/toolhive/guides-k8s/auth-k8s.mdx index 5bd47dc4..052eb8d4 100644 --- a/docs/toolhive/guides-k8s/auth-k8s.mdx +++ b/docs/toolhive/guides-k8s/auth-k8s.mdx @@ -28,7 +28,7 @@ You'll need: - Kubernetes cluster with RBAC enabled - ToolHive Operator installed (see - [Deploy the ToolHive Operator with Helm](./deploy-operator-helm.mdx)) + [Deploy the ToolHive Operator with Helm](./deploy-operator.mdx)) - `kubectl` access to your cluster ## Choose your authentication approach @@ -422,7 +422,7 @@ kubectl logs -n toolhive-system -l app.kubernetes.io/name=weather-server-k8s - For running MCP servers without authentication, see [Run MCP servers in Kubernetes](./run-mcp-k8s.mdx) - For ToolHive Operator installation, see - [Deploy the ToolHive Operator with Helm](./deploy-operator-helm.mdx) + [Deploy the ToolHive Operator with Helm](./deploy-operator.mdx) ## Troubleshooting diff --git a/docs/toolhive/guides-k8s/deploy-operator-helm.mdx b/docs/toolhive/guides-k8s/deploy-operator.mdx similarity index 100% rename from docs/toolhive/guides-k8s/deploy-operator-helm.mdx rename to docs/toolhive/guides-k8s/deploy-operator.mdx diff --git a/docs/toolhive/guides-k8s/deploy-registry.mdx b/docs/toolhive/guides-k8s/deploy-registry.mdx index 3503d291..6a9d201f 100644 --- a/docs/toolhive/guides-k8s/deploy-registry.mdx +++ b/docs/toolhive/guides-k8s/deploy-registry.mdx @@ -12,7 +12,7 @@ description: - [`kubectl`](https://kubernetes.io/docs/tasks/tools/) configured to communicate with your cluster - The ToolHive operator installed in your cluster (see - [Deploy the operator using Helm](./deploy-operator-helm.mdx)) + [Deploy the operator using Helm](./deploy-operator.mdx)) - A PostgreSQL database (recommended for production deployments) ## Overview @@ -57,8 +57,8 @@ flowchart LR You can create `MCPRegistry` resources in the namespaces where the ToolHive Operator is deployed. -See [Deploy the operator](./deploy-operator-helm.mdx#operator-deployment-modes) -to learn about the different deployment modes. +See [Deploy the operator](./deploy-operator.mdx#operator-deployment-modes) to +learn about the different deployment modes. To create a registry, define an `MCPRegistry` resource and apply it to your cluster. This minimal example creates a registry that syncs from the ToolHive @@ -619,8 +619,8 @@ feature. - [Kubernetes CRD reference](../reference/crd-spec.mdx#apiv1alpha1mcpregistry) - Reference for the `MCPRegistry` Custom Resource Definition (CRD) -- [Deploy the operator using Helm](./deploy-operator-helm.mdx) - Install the - ToolHive operator +- [Deploy the operator using Helm](./deploy-operator.mdx) - Install the ToolHive + operator - [Database configuration](../guides-registry/database.mdx) - Configure PostgreSQL storage diff --git a/docs/toolhive/guides-k8s/intro.mdx b/docs/toolhive/guides-k8s/intro.mdx index 490e23d3..d210c598 100644 --- a/docs/toolhive/guides-k8s/intro.mdx +++ b/docs/toolhive/guides-k8s/intro.mdx @@ -64,7 +64,7 @@ or Gateway. To learn how to expose your MCP servers and connect clients, see ## Installation -[Use Helm to install the ToolHive operator](./deploy-operator-helm.mdx) in your +[Use Helm to install the ToolHive operator](./deploy-operator.mdx) in your Kubernetes cluster. Helm simplifies the installation process and lets you manage the operator using Helm charts. diff --git a/docs/toolhive/guides-k8s/remote-mcp-proxy.mdx b/docs/toolhive/guides-k8s/remote-mcp-proxy.mdx index 7019d5da..b1b34736 100644 --- a/docs/toolhive/guides-k8s/remote-mcp-proxy.mdx +++ b/docs/toolhive/guides-k8s/remote-mcp-proxy.mdx @@ -56,7 +56,7 @@ spec and its capabilities are possible. - [`kubectl`](https://kubernetes.io/docs/tasks/tools/) configured to communicate with your cluster - The ToolHive operator installed in your cluster (see - [Deploy the operator using Helm](./deploy-operator-helm.mdx)) + [Deploy the operator using Helm](./deploy-operator.mdx)) - An OIDC identity provider (Keycloak, Okta, Azure AD, etc.) - Access to a remote MCP server that supports HTTP transport (SSE or Streamable HTTP) @@ -96,8 +96,8 @@ operator was deployed. - **Cluster mode (default)**: Create MCPRemoteProxy resources in any namespace - **Namespace mode**: Create MCPRemoteProxy resources only in allowed namespaces -See [Deploy the operator](./deploy-operator-helm.mdx#operator-deployment-modes) -to learn about the different deployment modes. +See [Deploy the operator](./deploy-operator.mdx#operator-deployment-modes) to +learn about the different deployment modes. ### Basic configuration @@ -657,8 +657,8 @@ feature in the ToolHive Registry Server. - [Kubernetes CRD reference](../reference/crd-spec.mdx#apiv1alpha1mcpremoteproxy) - Full MCPRemoteProxy specification -- [Deploy the operator using Helm](./deploy-operator-helm.mdx) - Install the - ToolHive operator +- [Deploy the operator using Helm](./deploy-operator.mdx) - Install the ToolHive + operator - [Run MCP servers in Kubernetes](./run-mcp-k8s.mdx) - Deploy local MCP servers ## Troubleshooting diff --git a/docs/toolhive/guides-k8s/run-mcp-k8s.mdx b/docs/toolhive/guides-k8s/run-mcp-k8s.mdx index 245534fa..4492232d 100644 --- a/docs/toolhive/guides-k8s/run-mcp-k8s.mdx +++ b/docs/toolhive/guides-k8s/run-mcp-k8s.mdx @@ -10,7 +10,7 @@ description: How to deploy MCP servers in Kubernetes using the ToolHive operator - [`kubectl`](https://kubernetes.io/docs/tasks/tools/) configured to communicate with your cluster - The ToolHive operator installed in your cluster (see - [Deploy the operator using Helm](./deploy-operator-helm.mdx)) + [Deploy the operator using Helm](./deploy-operator.mdx)) ## Overview @@ -117,8 +117,8 @@ deployed. - **Cluster mode (default)**: Create MCPServer resources in any namespace - **Namespace mode**: Create MCPServer resources only in allowed namespaces -See [Deploy the operator](./deploy-operator-helm.mdx#operator-deployment-modes) -to learn about the different deployment modes. +See [Deploy the operator](./deploy-operator.mdx#operator-deployment-modes) to +learn about the different deployment modes. To create an MCP server, define an `MCPServer` resource and apply it to your cluster. This minimal example creates the @@ -463,8 +463,8 @@ feature in the ToolHive Registry Server. - [Kubernetes CRD reference](../reference/crd-spec.mdx#apiv1alpha1mcpserver) - Reference for the `MCPServer` Custom Resource Definition (CRD) -- [Deploy the operator using Helm](./deploy-operator-helm.mdx) - Install the - ToolHive operator +- [Deploy the operator using Helm](./deploy-operator.mdx) - Install the ToolHive + operator - [Build MCP containers](../guides-cli/build-containers.mdx) - Create custom MCP server container images @@ -486,7 +486,7 @@ helm get values toolhive-operator -n toolhive-system Check the `operator.rbac.scope` and `operator.rbac.allowedNamespaces` properties. If the operator runs in `namespace` mode, add the namespace where you created the `MCPServer` to the `allowedNamespaces` list. See -[Operator deployment modes](./deploy-operator-helm.mdx#operator-deployment-modes). +[Operator deployment modes](./deploy-operator.mdx#operator-deployment-modes). If the operator runs in `cluster` mode (default) or the `MCPServer` is in an allowed namespace, check the operator logs and resource status: diff --git a/docs/toolhive/guides-k8s/telemetry-and-metrics.mdx b/docs/toolhive/guides-k8s/telemetry-and-metrics.mdx index 2c1b6296..6128477d 100644 --- a/docs/toolhive/guides-k8s/telemetry-and-metrics.mdx +++ b/docs/toolhive/guides-k8s/telemetry-and-metrics.mdx @@ -284,5 +284,5 @@ Telemetry adds minimal overhead when properly configured: of ToolHive's observability architecture - [Kubernetes CRD reference](../reference/crd-spec.mdx#apiv1alpha1mcpserver) - Reference for the `MCPServer` Custom Resource Definition (CRD) -- [Deploy the operator using Helm](./deploy-operator-helm.mdx) - Install the - ToolHive operator +- [Deploy the operator using Helm](./deploy-operator.mdx) - Install the ToolHive + operator diff --git a/docs/toolhive/guides-k8s/token-exchange-k8s.mdx b/docs/toolhive/guides-k8s/token-exchange-k8s.mdx index 469cf23d..781a37c6 100644 --- a/docs/toolhive/guides-k8s/token-exchange-k8s.mdx +++ b/docs/toolhive/guides-k8s/token-exchange-k8s.mdx @@ -19,7 +19,7 @@ Before you begin, make sure you have: - Kubernetes cluster with RBAC enabled - ToolHive Operator installed (see - [Deploy the ToolHive Operator with Helm](./deploy-operator-helm.mdx)) + [Deploy the ToolHive Operator with Helm](./deploy-operator.mdx)) - `kubectl` access to your cluster - An identity provider that supports [RFC 8693](https://datatracker.ietf.org/doc/html/rfc8693) token exchange (such diff --git a/docs/toolhive/tutorials/quickstart-k8s.mdx b/docs/toolhive/tutorials/quickstart-k8s.mdx index bc18d3ec..300a3102 100644 --- a/docs/toolhive/tutorials/quickstart-k8s.mdx +++ b/docs/toolhive/tutorials/quickstart-k8s.mdx @@ -436,9 +436,8 @@ Here are some next steps to explore: - Learn about [advanced MCP server configurations](../guides-k8s/run-mcp-k8s.mdx) for production deployments -- Learn more about - [Helm deployment options](../guides-k8s/deploy-operator-helm.mdx) and - configuration +- Learn more about [Helm deployment options](../guides-k8s/deploy-operator.mdx) + and configuration - Integrate MCP servers with your existing Kubernetes applications - Try deploying other MCP servers from the ToolHive registry diff --git a/sidebars.ts b/sidebars.ts index 34d3158a..49827215 100644 --- a/sidebars.ts +++ b/sidebars.ts @@ -152,7 +152,7 @@ const sidebars: SidebarsConfig = { }, items: [ 'toolhive/guides-k8s/intro', - 'toolhive/guides-k8s/deploy-operator-helm', + 'toolhive/guides-k8s/deploy-operator', 'toolhive/guides-k8s/run-mcp-k8s', 'toolhive/guides-k8s/remote-mcp-proxy', 'toolhive/guides-k8s/connect-clients', diff --git a/vercel.json b/vercel.json index db0a7e85..11a5e73a 100644 --- a/vercel.json +++ b/vercel.json @@ -25,6 +25,11 @@ "source": "/toolhive/guides-mcp/meta-mcp", "destination": "/toolhive/tutorials/mcp-optimizer", "permanent": true + }, + { + "source": "/toolhive/guides-k8s/deploy-operator-helm", + "destination": "/toolhive/guides-k8s/deploy-operator", + "permanent": true } ], "installCommand": "dnf install -q -y jq && npm install",