ping-se-cluster-deploy

Deploy applications to Ping's shared SE Kubernetes cluster with kubectl and GHCR.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Getting first-time access to Ping's shared SE DevOps Kubernetes cluster (ping-dev-aws-us-east-2) and deploying demo or POC applications onto it involves scattered tribal knowledge: DEVHELP JIRA requests, Secret Server kubeconfigs, kubelogin OIDC authentication, GHCR token refreshes, and mandatory teardown discipline. This Skill consolidates that entire workflow into one operational guide. ## Core Features & Use Cases - First-time cluster access: Step-by-step instructions for requesting a namespace via DEVHELP JIRA, installing kubelogin/jwt-cli/kubectx, and installing a kubeconfig from Secret Server. - Deploy routine: Covers GHCR authentication refresh, image build/push, kubectl manifest application, and health verification. - Troubleshooting table: Maps common symptoms (missing context, GHCR push denied, OIDC timeouts, 503s after deploy) to concrete fixes. - Use Case: An SE finishes a local demo and needs to push it to the shared cluster before a customer call. The Skill walks them through context switching, GHCR login, deployment, verification, and the required undeploy afterward. ## Quick Start Ask the agent to help you deploy your app to the Ping SE shared cluster and it will verify your kubectl context, refresh GHCR credentials, apply your manifests, and remind you to undeploy when finished.

Frequently Asked Questions about ping-se-cluster-deploy

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

FAQPage Schema
How do I get access to the Ping SE shared Kubernetes cluster?▼

File a DEVHELP JIRA service request titled "Grant Access to AWS GTE K8's Cluster" for cluster ping-dev-aws-us-east-2 with your Ping email. Then download your kubeconfig from Secret Server, install it to ~/.kube/config, and authenticate via kubelogin's PingOne browser login.

How do I push Docker images to GHCR for a Kubernetes deploy?▼

Refresh your GitHub token with the write:packages scope using gh auth refresh, then pipe gh auth token into docker login ghcr.io. The token expires, so repeat this before every deploy session before building and pushing images.

Why does kubectl show no context for the SE cluster?▼

A missing SE context means the kubeconfig was never installed or was overwritten. Re-download the config from Secret Server, place it at ~/.kube/config with chmod 600, and keep a backup copy outside the default location in case the entry is rotated.

Why does kubectl give context deadline exceeded on the shared cluster?▼

This happens when the OIDC browser login popup was never completed. Re-run the kubectl command that triggers the PingOne login prompt and finish the browser authentication to obtain a valid token.

Do I need to undeploy my app from the shared SE cluster?▼

Yes, undeploying is mandatory because the cluster is shared across all SEs. Run kubectl delete with your manifests against your namespace when the demo session ends, or you risk losing publishing rights on the cluster.