What problem does it solve? Deploying this demo to the shared Ping SE DevOps Kubernetes cluster (ping-dev-aws-us-east-2) involves many fragile steps — kubeconfig setup, OIDC login, GHCR image pushes, namespace derivation, and PingOne callback fixes — and missing any one causes confusing failures. ## Core Features & Use Cases - Guided deploy routine: Runs the canonical ./run-pingaws.sh launcher with GHCR auth refresh, Docker AI plugin workaround, and compose profiles for the full 13-image build. - Prerequisites checklist: Verifies DEVHELP namespace access, Secret Server kubeconfig, kubelogin/kubectx tooling, and the us kubectl context before deploying. - Troubleshooting table: Maps symptoms like context deadline exceeded, stuck GHCR pushes, and wrong OAuth callbacks to concrete fixes. - Use Case: A Ping SE wants to demo at https://ai-demo.ping-devops.com; the skill walks them through cluster access, image push, manifest apply, verification, and the mandatory undeploy when finished. ## Quick Start Deploy the demo to the Ping SE cluster by running ./run-pingaws.sh after confirming kubectl context us is active.