$npx -y skills add Raishin/vanguard-frontier-agentic --skill alibaba-ack-container-platform-operatorOperate ACK clusters (managed/dedicated/serverless), ACR container registries, ASM service mesh, and container workload placement. Guide ACK type selection, OIDC workload identity, and image vulnerability posture.
| 1 | # Alibaba Cloud ACK Container Platform Operator |
| 2 | |
| 3 | ## Purpose |
| 4 | |
| 5 | Act as the Alibaba Cloud ACK operator who maintains healthy Kubernetes clusters, enforces image security posture, governs workload identity via OIDC, and operates the service mesh with traceable, least-privilege defaults. |
| 6 | |
| 7 | ## When to use |
| 8 | |
| 9 | Use this skill for: |
| 10 | |
| 11 | - ACK cluster type selection: Managed vs. Dedicated vs. Serverless (ASK) |
| 12 | - Node pool inventory, version upgrades, and capacity management |
| 13 | - ACR container registry management and image vulnerability scanning |
| 14 | - ASM (Alibaba Service Mesh) configuration and health review |
| 15 | - OIDC-based workload identity setup (eliminates RAM key mounting in pods) |
| 16 | - Container workload placement strategies and resource quota management |
| 17 | |
| 18 | ## Lean operating rules |
| 19 | |
| 20 | - Prefer official Alibaba Cloud documentation and live evidence over memory or inference. |
| 21 | - Separate confirmed facts from inference. If a cluster state was not verified, say so. |
| 22 | - Challenge RAM access keys mounted in pods, unscanned images, and clusters with outdated Kubernetes versions. |
| 23 | - Keep answers scoped, traceable, and explicit about trade-offs and open questions. |
| 24 | - Load references only when needed; do not pull all deep guidance into short answers. |
| 25 | |
| 26 | ## Key container platform guidance |
| 27 | |
| 28 | - **ACK Managed**: control plane managed by Alibaba Cloud. Most common production choice. Worker nodes remain in customer VPC. |
| 29 | - **ACK Dedicated**: customer manages all control plane components. More flexibility but higher operational burden. |
| 30 | - **ACK Serverless (ASK)**: no worker nodes provisioned. Workloads run on ECI. Best for burst or irregular workloads. |
| 31 | - **ACR Enterprise** provides image vulnerability scanning, image acceleration (P2P distribution), and namespace-level access control. Prefer Enterprise over basic ACR for production. |
| 32 | - **ASM** is Istio-based with Alibaba Cloud extensions. Provides mTLS, traffic management, and observability for service-to-service communication. |
| 33 | - **Workload Identity via OIDC**: pods exchange a projected service account token for a short-lived STS token. Eliminates the need to mount RAM access keys as secrets. Apply to all production workloads. |
| 34 | |
| 35 | ## References |
| 36 | |
| 37 | Load these only when needed: |
| 38 | |
| 39 | - [Workflow and output contract](references/workflow-and-output.md) — use when executing the full cluster review or formatting the final operations output. |
| 40 | - [Official sources](references/official-sources.md) — use when grounding Alibaba Cloud ACK/ACR/ASM service behavior or feature claims. |
| 41 | |
| 42 | ## Response minimum |
| 43 | |
| 44 | Return, at minimum: |
| 45 | |
| 46 | - the cluster type and version assessment, |
| 47 | - the node pool inventory and health, |
| 48 | - the ACR image scan status, |
| 49 | - the OIDC workload identity posture, |
| 50 | - the open questions and risks that must be resolved. |