Skip to content

Commit 0e38579

Browse files
committed
Improve kubernetes documentation.
Main change is the addition of a note to clarify how to authenticate with Helm. Not really an issue, but I ran into this because my token was expired and had to go through docs again.
1 parent 1151062 commit 0e38579

File tree

2 files changed

+11
-8
lines changed

2 files changed

+11
-8
lines changed

docs/toolhive/kubernetes/deploy-operator-helm.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,13 @@ Kubernetes cluster.
1919

2020
## Install the operator
2121

22+
:::note
23+
24+
You must first be authenticated to ghcr.io following
25+
[these instructions](https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-container-registry#authenticating-with-a-personal-access-token-classic).
26+
27+
:::
28+
2229
To install the ToolHive operator using Helm and the default settings, follow
2330
these steps:
2431

docs/toolhive/kubernetes/intro.md

Lines changed: 4 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -51,13 +51,9 @@ flowchart TB
5151

5252
## Installation
5353

54-
To install the ToolHive operator in your Kubernetes cluster, use Helm. Helm
55-
simplifies the installation process and lets you manage the operator using Helm
56-
charts.
57-
58-
[Deploy the operator using Helm](./deploy-operator-helm.md)
54+
[Use Helm to install the ToolHive operator](./deploy-operator-helm.md) in your
55+
Kubernetes cluster. Helm simplifies the installation process and lets you manage
56+
the operator using Helm charts.
5957

6058
Once the operator is installed, you can create and manage MCP servers using the
61-
`MCPServer` custom resource.
62-
63-
[Run MCP servers in Kubernetes](./run-mcp-k8s.md)
59+
[`MCPServer` custom resource](./run-mcp-k8s.md).

0 commit comments

Comments
 (0)