privilege-mcpgw-agent-k8s

Deploy and troubleshoot the PingOne Privilege AI Gateway on Kubernetes with Helm.

1|Updated Jun 25, 2026
One-click install
npx skills add https://github.com/curtismu7/AI-DEMO2 --skill privilege-mcpgw-agent-k8s-curtismu7
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: privilege-mcpgw-agent-k8s
Source: https://github.com/curtismu7/AI-DEMO2/tree/main/.claude/skills/privilege-mcpgw-agent-k8s
Command: npx skills add https://github.com/curtismu7/AI-DEMO2 --skill privilege-mcpgw-agent-k8s-curtismu7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deploying the PingOne Privilege AI Gateway (agentless MCP gateway) on a Kubernetes cluster involves non-obvious failure modes — SSE vs /mcp transport mismatches, stale packaged Helm charts silently dropping sidecars, in-memory DCR client loss on restart, and misleading policy-denial errors — that this Skill diagnoses and resolves with observed, verified commands. ## Core Features & Use Cases - Gateway Deployment: Install and upgrade the agentless-mcpgw Helm release with OIDC secrets, enrollment tokens, and ingress configuration on the SE DevOps cluster. - Agentic App Registration: Register MCP servers in the Privilege console using the correct /sse backend URL, mesh cluster ID, and sidecar pattern via extraContainers. - Symptom Diagnosis: Map errors like "Unknown client", "Gateway Unreachable — initialize: Unauthorized", and "Access Denied for" to their real root causes using gateway logs. - Use Case: A client hangs forever connecting to the gateway — the Skill identifies that svc.cluster.local only resolves inside the cluster and provides the correct external client URL and port-forward workaround. ## Quick Start Diagnose why my MCP client gets "Gateway Unreachable — Error discovering MCP server: calling initialize: Unauthorized" when registering my server with the Privilege gateway.

Frequently Asked Questions about privilege-mcpgw-agent-k8s

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy the PingOne Privilege AI Gateway on Kubernetes?▼

Install the agentless-mcpgw Helm chart into the ping-devops-curtismuir namespace with a secrets file containing the proxyToken from the Privilege console and OIDC client settings. Verify success by finding LinkStatus:Active in the gateway logs.

Why does the Privilege console show Gateway Unreachable with initialize Unauthorized?▼

This error means the MCP server was registered with a /mcp URL instead of /sse. The gateway's discovery client uses the SSE transport and waits for an endpoint event that streamable-HTTP never sends, so re-register the backend with the /sse path and restart the gateway.

How do I add a new MCP server to the Privilege gateway?▼

Add an entry to extraContainers in a values file with its own port, run helm package to keep the .tgz in sync, dry-run the upgrade to verify the render, then upgrade and register it in the console pointing at http://localhost:<port>/sse.

Why does my MCP client show Unknown client after a gateway restart?▼

The gateway's DCR registry is in memory, so every restart forgets all dynamically registered clients. The client must re-register; the demo BFF handles this automatically, but other clients must be deleted and re-added manually.

What does Access Denied mean in the Privilege gateway logs?▼

Access Denied for means the user is synced into Privilege but no policy on that specific Agentic App covers them, since policies are per-app and time-boxed. User not found in system instead means the user is not synced via the PingOne group membership policy.

Why did my Helm upgrade drop the MCP sidecar containers?▼

The packaged .tgz went stale after template edits, so the upgrade re-rendered the Deployment without extraContainers and imagePullSecrets even though helm get values still showed them. Repackage the chart after every template edit and verify with a dry-run grep before upgrading.