fix: improve kubernetes mcp server configuration for archestra platform

[Aqil-Ahmad]

/fixes archestra-ai/archestra#1485

i updated the kubernetes mcp server evaluation to include all 23 tools, user-configurable options, and added
different installation permutations.

/claim archestra-ai/archestra#1485

/claim #1485

[vercel]

@Aqil-Ahmad is attempting to deploy a commit to the Archestra projects Team on Vercel.

A member of the Team first needs to authorize it.

[CLAassistant]

All committers have signed the CLA.

[Aqil-Ahmad]

i will add the video demo shortly.

[Copilot]

Pull request overview

This pull request significantly enhances the Kubernetes MCP server evaluation by adding comprehensive configuration options, documenting all 23 available tools, and providing multiple installation permutations for different use cases.

Key Changes:

• Added complete tool definitions for all 23 Kubernetes management tools (kubectl operations, Helm operations, node management, port forwarding, etc.)
• Expanded user configuration with 9 configurable options covering authentication, namespace selection, security modes, and performance tuning
• Introduced 4 installation permutations (default, readonly, non-destructive, production) to support different deployment scenarios
• Enhanced description with detailed feature list and improved discoverability through comprehensive keywords

[ashlkv]

@Aqil-Ahmad Unfortunately when I try to install kubernetes MCP with the updated catalog entry, it's an error. When I'm installing, I'm specifiying those vars:

K8S_CONTEXT: kind-archestra-dev
KUBECONFIG_PATH: <path to local-kubeconfig.yaml>

The error in logs:

@backend:dev: [12:34:56 UTC] INFO: Starting MCP server pod: id="5d75c96d-5c15-4fe2-91d1-96e33d6047a2", name="flux159__mcp-server-kubernetes-lh4UDkH3qvssdIIKRcHWA7Cm1aNLbmVX"
@backend:dev: [12:34:56 UTC] INFO: Creating pod mcp-flux159mcp-server-kubernetes-lh4udkh3qvssdiikrchwa7cm1anlbmvx for MCP server flux159__mcp-server-kubernetes-lh4UDkH3qvssdIIKRcHWA7Cm1aNLbmVX
@backend:dev: [12:34:56 UTC] INFO: Pod mcp-flux159mcp-server-kubernetes-lh4udkh3qvssdiikrchwa7cm1anlbmvx created, will check status asynchronously
@backend:dev: [12:34:56 UTC] INFO: Pod mcp-flux159mcp-server-kubernetes-lh4udkh3qvssdiikrchwa7cm1anlbmvx is now running
@backend:dev: [12:34:56 UTC] INFO: Successfully started MCP server pod 5d75c96d-5c15-4fe2-91d1-96e33d6047a2 (flux159__mcp-server-kubernetes-lh4UDkH3qvssdIIKRcHWA7Cm1aNLbmVX)
@backend:dev: [12:34:56 UTC] INFO: Started K8s pod for local MCP server: flux159__mcp-server-kubernetes-lh4UDkH3qvssdIIKRcHWA7Cm1aNLbmVX
@backend:dev: [12:34:56 UTC] INFO: Skipping synchronous tool fetch for local server: flux159__mcp-server-kubernetes-lh4UDkH3qvssdIIKRcHWA7Cm1aNLbmVX. Tools will be fetched asynchronously.
@backend:dev: [12:34:56 UTC] INFO: Waiting for pod to be ready: flux159__mcp-server-kubernetes-lh4UDkH3qvssdIIKRcHWA7Cm1aNLbmVX
@backend:dev: [12:34:58 UTC] ERROR: Failed to fetch tools from local server flux159__mcp-server-kubernetes-lh4UDkH3qvssdIIKRcHWA7Cm1aNLbmVX: Pod mcp-flux159mcp-server-kubernetes-lh4udkh3qvssdiikrchwa7cm1anlbmvx failed: CreateContainerConfigError - secret "mcp-server-5d75c96d-5c15-4fe2-91d1-96e33d6047a2-secrets" not found

[Aqil-Ahmad]

@ashlkv i might be missing something. but it worked for me

[ashlkv]

@Aqil-Ahmad Got it. The error happened because I did not specify the token and there was a bug in platform with empty "sensitive" type env vars. I'm specifying only the following vars.

K8S_CONTEXT: kind-archestra-dev
KUBECONFIG_PATH: <path to local-kubeconfig.yaml>

I'm not 100% sure if they are sufficient, because I'm getting an error trying to list pods. I'm investigating.

[Aqil-Ahmad]

@ashlkv i see your pr was merged and the issue is now closed. just wanted to check if the bounty will be awarded to you, or if it will be shared?

[iskhakov]

/reward 50

[Aqil-Ahmad]

@iskhakov thanks for the reward. could you let me know how to claim it or if there's anything i need to do from my side?

[iskhakov]

/claim #1485

[iskhakov]

/claim #1485

[iskhakov]

/reward 50

[iskhakov]

closed and rewarded. See original issue

[joeyorlando]

closed and rewarded. See original issue

@iskhakov good to close this PR?