-
Notifications
You must be signed in to change notification settings - Fork 178
Adding first set of user documentation #411
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
For other "agents", like VS Code, or even Claude Desktop, I think creating screenshots makes more sense, rather than for the initial "Claude Code CLI", @manusa |
…etes, as well as with 'claude code CLI' Signed-off-by: Matthias Wessendorf <[email protected]>
|
I'll check thoroughly in a bit. In the meantime, and related to his PR, one of the things I wanted to do was to update the main README.md Getting Started section to be more like the one in https://github.com/microsoft/playwright-mcp, with collapsible sections for each MCP Host/Client. In scope of this PR (since it's focusing on Claude Code), maybe we can already add a collapsible <details>
<summary>Claude Code</summary>
Follow the [dedicated MCP getting started guide]($linkToClaudeCodeGettingStarted) in our [user documentation].($linkToDocs)
</details>to the main README.md too. |
|
This looks great @matzew ! One question is, can we mention somewhere that all of the serviceaccount/custom kubeconfig is not technically necessary, but is recommended? |
|
Ah, sure!
Sent from Gmail Mobile
…On Mon 27. Oct 2025 at 13:41, Calum Murray ***@***.***> wrote:
*Cali0707* left a comment (containers/kubernetes-mcp-server#411)
<#411 (comment)>
This looks great @matzew <https://github.com/matzew> ! One question is,
can we mention somewhere that all of the serviceaccount/custom kubeconfig
is not technically necessary, but is recommended?
—
Reply to this email directly, view it on GitHub
<#411 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABGPTWDYYR7HZCICB24CVD3ZYHHBAVCNFSM6AAAAACKJVUCFSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTINJRGA4DIMBSGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
@Cali0707 Added a note |
|
@manusa added the For a general overhaul, we can use a separate PR - but I like the pattern of doing these sections! |
manusa
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Besides the comment about the namespace flag, everything else looks good. Thx!!!
* note on recommendation about use SA versus exciting (default) kubeconfig * adding a collapsible section * removed incorrect args Signed-off-by: Matthias Wessendorf <[email protected]>
|
@manusa updated an rebased |
Cali0707
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
manusa
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thx!
yes, but that is separate steps. I was thinking about that too |
There's an old branch of mine (https://github.com/containers/kubernetes-mcp-server/tree/doc/docusaurus) from when this was still a personal PoC. I think we should create some sort of website but discuss exactly how we want to do this (also considering the downstream implications). |
Adding initial set of document, adding a README as an overview for all of the content, and specific guides
Next PR will add VS code, similar to this blog
The Kubernetes guide is inspired by the referenced blog post, but does focus on just
kubernetes