Skip to content

Commit eada357

Browse files
committed
Review: note on recommendation about use SA versus exciting (default) kubeconfig
Signed-off-by: Matthias Wessendorf <[email protected]>
1 parent 4ca578d commit eada357

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

docs/GETTING_STARTED_KUBERNETES.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,9 @@
22

33
This guide walks you through the foundational setup for using the Kubernetes MCP Server with your Kubernetes cluster. You'll create a dedicated, read-only ServiceAccount and generate a secure kubeconfig file that can be used with various MCP clients.
44

5-
> **Note:** After completing this guide, continue with the [Claude Code CLI guide](GETTING_STARTED_CLAUDE_CODE.md). See the [docs README](README.md) for all available guides.
5+
> **Note:** This setup is **recommended for production use** but not strictly required. The MCP Server can use your existing kubeconfig file (e.g., `~/.kube/config`), but using a dedicated ServiceAccount with limited permissions follows the principle of least privilege and is more secure.
6+
7+
> **Next:** After completing this guide, continue with the [Claude Code CLI guide](GETTING_STARTED_CLAUDE_CODE.md). See the [docs README](README.md) for all available guides.
68
79
## What You'll Create
810

0 commit comments

Comments
 (0)