From vanguard-frontier-agentic
Gates GKE node pool upgrades, cluster control-plane version changes, and deployment rollouts against PDB audit, surge settings review, and rollback posture verification before production mutations proceed.
How this skill is triggered — by the user, by Claude, or both
Slash command
/vanguard-frontier-agentic:gcp-live-gke-rollout-guardThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Act as the guarded live GCP operator for gcp-live-gke-rollout-guard work. Gate GKE deployment mutations, node pool upgrades, and cluster control-plane version changes. Insist on PDB audit and rollback posture evidence before execution, and treat any ambiguous approval or target as a stop condition.
Act as the guarded live GCP operator for gcp-live-gke-rollout-guard work. Gate GKE deployment mutations, node pool upgrades, and cluster control-plane version changes. Insist on PDB audit and rollback posture evidence before execution, and treat any ambiguous approval or target as a stop condition.
Use this skill when:
Do not use this skill when:
Before executing any GKE mutation, verify all of the following:
gcloud container clusters describe <CLUSTER> --region <REGION> --project <PROJECT> and confirm the cluster name, version, and region match the intended target.gcloud auth list and gcloud config get-value account to confirm the active identity has the required role.kubectl get pdb --all-namespaces and confirm no PDB has DISRUPTIONS ALLOWED: 0 for workloads running on the affected node pool.maxSurge and maxUnavailable settings on the node pool are appropriate for the workload disruption tolerance.kubectl rollout history deployment/<NAME> -n <NAMESPACE> to document the pre-change state for Deployment rollouts.The operator must explicitly state all of the following before any mutation is executed:
<CLUSTER_NAME> in project <PROJECT_ID>, region <REGION>."<TARGET_VERSION> and I understand node pool upgrades cannot be downgraded."roles/container.clusterAdmin for mutation).gcloud container node-pools upgrade <POOL> --cluster <CLUSTER> --region <REGION> --project <PROJECT>gcloud container clusters upgrade <CLUSTER> --master --cluster-version <VERSION> --region <REGION> --project <PROJECT>kubectl set image deployment/<NAME> <CONTAINER>=<IMAGE> -n <NAMESPACE>kubectl rollout status deployment/<NAME> -n <NAMESPACE> or gcloud container operations describe <OPERATION_ID>.Ready status and all workloads are running post-upgrade.kubectl rollout undo deployment/<NAME> -n <NAMESPACE>gcloud container clusters describe <CLUSTER> — confirm currentMasterVersion matches target.gcloud container node-pools describe <POOL> --cluster <CLUSTER> — confirm version matches target.kubectl get nodes — confirm all nodes show Ready with the new version.kubectl get pods --all-namespaces — confirm no pods in CrashLoopBackOff or Pending state.kubectl get pdb --all-namespaces — confirm all PDBs still show healthy disruption budgets.npx claudepluginhub raishin/vanguard-frontier-agentic --plugin vanguard-frontier-agenticGates ACK cluster version upgrades, node pool scaling, and deployment rollouts against PodDisruptionBudget checks, rollback posture, and explicit operator approval. Requires PDB audit and RAM principal confirmation before mutation.
Provides copy-pasteable production-grade Kubernetes YAML patterns (Deployments, Probes, RBAC, HPA, Jobs) and kubectl debugging commands for managing workloads.
Implements rollback procedures for Kubernetes, ECS, Lambda, and cloud VM deployments. Detects failures via monitoring and health checks, reverts to stable versions, verifies success, and generates reports.