Skip to content

Commit b16ccb5

Browse files
authored
Fix minor typo in Vault tutorial, add missing CRDs upgrade step (#174)
* Fix container name for verification step * Add CRDs to upgrade steps, bump example versions --------- Signed-off-by: Dan Barr <[email protected]> Co-authored-by: Dan Barr <[email protected]>
1 parent b9dc6b8 commit b16ccb5

File tree

2 files changed

+18
-10
lines changed

2 files changed

+18
-10
lines changed

docs/toolhive/guides-k8s/deploy-operator-helm.md

Lines changed: 11 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ chart. To install a specific version, append `--version <VERSION>` to the
3333
command, for example:
3434

3535
```bash
36-
helm upgrade -i toolhive-operator-crds oci://ghcr.io/stacklok/toolhive/toolhive-operator-crds --version 0.0.7
36+
helm upgrade -i toolhive-operator-crds oci://ghcr.io/stacklok/toolhive/toolhive-operator-crds --version 0.0.21
3737
```
3838

3939
## Install the operator
@@ -52,7 +52,7 @@ chart. To install a specific version, append `--version <VERSION>` to the
5252
command, for example:
5353

5454
```bash
55-
helm upgrade -i toolhive-operator oci://ghcr.io/stacklok/toolhive/toolhive-operator -n toolhive-system --create-namespace --version 0.1.1
55+
helm upgrade -i toolhive-operator oci://ghcr.io/stacklok/toolhive/toolhive-operator -n toolhive-system --create-namespace --version 0.2.10
5656
```
5757

5858
Verify the installation:
@@ -81,7 +81,7 @@ and set a specific ToolHive version, create a `values.yaml` file:
8181
```yaml title="values.yaml"
8282
operator:
8383
replicaCount: 2
84-
toolhiveRunnerImage: ghcr.io/stacklok/toolhive:v0.1.8 # or `latest`
84+
toolhiveRunnerImage: ghcr.io/stacklok/toolhive:v0.2.17 # or `latest`
8585
```
8686
8787
Install the operator with your custom values:
@@ -222,8 +222,14 @@ kubectl logs -n toolhive-system <TOOLHIVE_OPERATOR_POD_NAME>
222222

223223
## Upgrade the operator
224224

225-
To upgrade the ToolHive operator to a new version, use the same command you used
226-
to install it:
225+
To upgrade the ToolHive operator to a new version, use the same commands you
226+
used to install it. First, upgrade the CRDs if a new version is available:
227+
228+
```bash
229+
helm upgrade -i toolhive-operator-crds oci://ghcr.io/stacklok/toolhive/toolhive-operator-crds
230+
```
231+
232+
Then upgrade the operator itself:
227233

228234
```bash
229235
helm upgrade toolhive-operator oci://ghcr.io/stacklok/toolhive/toolhive-operator -n toolhive-system --reuse-values

docs/toolhive/tutorials/vault-integration.mdx

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -6,11 +6,13 @@ description:
66
---
77

88
This tutorial shows how to integrate HashiCorp Vault with the ToolHive
9-
Kubernetes Operator to securely manage secrets for your MCP servers. Using
10-
Vault's Agent Injector, you can automatically provision secrets into MCP server
11-
pods without exposing sensitive data in your Kubernetes manifests.
9+
Kubernetes Operator to securely manage secrets for your MCP servers. Using the
10+
[Vault Agent Injector](https://developer.hashicorp.com/vault/docs/deploy/kubernetes/injector),
11+
you can automatically provision secrets into MCP server pods without exposing
12+
sensitive data in your Kubernetes manifests.
1213

13-
As an example, we'll be deploying a GitHub MCP server.
14+
To demonstrate this integration, you will deploy a GitHub MCP server that
15+
retrieves a GitHub personal access token (PAT) from Vault.
1416

1517
:::info[Prerequisites]
1618

@@ -255,7 +257,7 @@ MCP_POD_NAME=$(kubectl get pods -ntoolhive-system \
255257
-ojsonpath='{.items[0].metadata.name}')
256258
257259
# Verify the Vault Agent wrote the secret file
258-
kubectl exec -n toolhive-system "$PROXY_POD_NAME" -c toolhive -- \
260+
kubectl exec -n toolhive-system "$PROXY_POD_NAME" -c vault-agent -- \
259261
cat /vault/secrets/github-config
260262
261263
# Check that the environment variable is available to the MCP server

0 commit comments

Comments
 (0)