Claude Cursor GitHub Copilot Skill

alibaba-ack-container-platform-operator

Operate 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.

LLM Mart · 0 points · 0 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download vincentchuwaichow-vanguard-frontier-agentic-skills_alibaba_alibaba-ack-container-platform-operator-febe32a.zip · 4 KB

vincentchuwaichow/vanguard-frontier-agentic 24 3 forks Apache-2.0 Updated 1d ago

Part of vincentchuwaichow/vanguard-frontier-agentic — 293 skills

Install

skills CLI

npx skills add https://github.com/VincentChuWaiChow/vanguard-frontier-agentic/tree/master/skills/alibaba/alibaba-ack-container-platform-operator

Claude Code

claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install vincentchuwaichow-vanguard-frontier-agentic@llmmart

Git git clone https://github.com/VincentChuWaiChow/vanguard-frontier-agentic.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole vincentchuwaichow/vanguard-frontier-agentic collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Alibaba Cloud ACK Container Platform Operator

Purpose

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.

When to use

Use this skill for:

ACK cluster type selection: Managed vs. Dedicated vs. Serverless (ASK)
Node pool inventory, version upgrades, and capacity management
ACR container registry management and image vulnerability scanning
ASM (Alibaba Service Mesh) configuration and health review
OIDC-based workload identity setup (eliminates RAM key mounting in pods)
Container workload placement strategies and resource quota management

Lean operating rules

Prefer official Alibaba Cloud documentation and live evidence over memory or inference.
Separate confirmed facts from inference. If a cluster state was not verified, say so.
Challenge RAM access keys mounted in pods, unscanned images, and clusters with outdated Kubernetes versions.
Keep answers scoped, traceable, and explicit about trade-offs and open questions.
Load references only when needed; do not pull all deep guidance into short answers.

Key container platform guidance

ACK Managed: control plane managed by Alibaba Cloud. Most common production choice. Worker nodes remain in customer VPC.
ACK Dedicated: customer manages all control plane components. More flexibility but higher operational burden.
ACK Serverless (ASK): no worker nodes provisioned. Workloads run on ECI. Best for burst or irregular workloads.
ACR Enterprise provides image vulnerability scanning, image acceleration (P2P distribution), and namespace-level access control. Prefer Enterprise over basic ACR for production.
ASM is Istio-based with Alibaba Cloud extensions. Provides mTLS, traffic management, and observability for service-to-service communication.
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.

References

Load these only when needed:

Workflow and output contract — use when executing the full cluster review or formatting the final operations output.
Official sources — use when grounding Alibaba Cloud ACK/ACR/ASM service behavior or feature claims.

Response minimum

Return, at minimum:

the cluster type and version assessment,
the node pool inventory and health,
the ACR image scan status,
the OIDC workload identity posture,
the open questions and risks that must be resolved.

Files (vanguard-frontier-agentic)

references

official-sources.md 888 B

# Official sources

Use this reference only when you need source grounding for Alibaba Cloud ACK/ACR/ASM service behavior or the detailed source list.

## Alibaba Cloud documentation

Use these as starting points, not as proof of the user's live Alibaba Cloud state:
- https://www.alibabacloud.com/help/en/ack
- https://www.alibabacloud.com/help/en/acr
- https://www.alibabacloud.com/help/en/asm
- https://www.alibabacloud.com/help/en/eci
- https://www.alibabacloud.com/help/en/ack/ack-managed-clusters/user-guide/use-oidc-token-to-grant-pod-ram-permissions

## Grounding rule

Official documentation explains Alibaba Cloud service behavior and feature availability. It does not prove the user's current account, region, quota, resource configuration, pricing, or operational state. Prefer live Alibaba Cloud console evidence or sanitized user-provided evidence for current-state claims.

workflow-and-output.md 2.3 KB

# Workflow and output contract

Use this reference only when performing a full cluster operations review, upgrade assessment, or production-readiness pass.

## Review domains

Check these areas before giving a verdict:

- ACK cluster type, Kubernetes version, and upgrade path
- Node pool configuration, auto-repair, and capacity
- ACR registry tier, image vulnerability scan results, and image signing
- ASM service mesh version, mTLS enforcement, and policy coverage
- OIDC workload identity configuration and pod-level RAM role assignments
- Resource quotas, LimitRange, and namespace isolation

## Safe workflow

1. **Frame scope**
   - Cluster name, type, region, and environment:
   - Business criticality and owner:
   - Compliance requirements:
   - Required outcome:
   - Explicit non-goals:
2. **Collect evidence**
   - Prefer live ACK console or kubectl/API evidence if available.
   - Otherwise inspect IaC, sanitized user evidence, or official Alibaba Cloud docs.
   - Label each finding as `live evidence`, `repo evidence`, `user-provided evidence`, `documentation-based`, or `inference`.
3. **Stress-test risk**
   - What workloads use RAM access keys instead of OIDC?
   - What images have unresolved critical CVEs?
   - What node pools are on end-of-support Kubernetes versions?
   - What ASM policies are missing mTLS enforcement?
4. **Recommend the smallest safe action**
   - Prefer canary or blue-green upgrade strategies before full cluster upgrade.
   - If the safest action is to stop and gather evidence, say that plainly.

## Output contract

Return this structure:
```markdown
# Alibaba Cloud ACK Platform Review: <scope>
## Executive verdict
- Status: HEALTHY / ATTENTION NEEDED / ACTION REQUIRED
- Biggest risk:
- Evidence level:
## Cluster type and version
- Cluster type:
- Kubernetes version:
- Upgrade path:
## Node pool inventory
| Pool name | Node count | Instance type | Version | Health |
|---|---|---|---|---|
## ACR registry and image scan status
- Registry tier:
- Vulnerability findings:
- Image signing:
## ASM service mesh health
- ASM version:
- mTLS enforcement:
- Policy gaps:
## OIDC workload identity
- OIDC provider configured:
- Workloads using OIDC vs. RAM keys:
## Recommendations
1. <action> — owner: <owner>, validation: <check>, rollback: <rollback>
## Open risks
- <risk or explicit none>
```

metadata.json 1.1 KB

{
  "id": "alibaba-ack-container-platform-operator",
  "name": "Alibaba Cloud ACK Container Platform Operator",
  "type": "skill",
  "provider": "alibaba",
  "harnesses": [
    "codex",
    "claude-code",
    "cursor",
    "gemini",
    "kiro",
    "other"
  ],
  "summary": "Operate 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.",
  "source_type": "original",
  "official_docs": [
    "https://www.alibabacloud.com/help/en/ack",
    "https://www.alibabacloud.com/help/en/acr",
    "https://www.alibabacloud.com/help/en/asm"
  ],
  "security_notes": "Require OIDC workload identity for all production workloads — do not approve RAM access key mounting in pods. Require ACR Enterprise vulnerability scanning before deploying images to production clusters. Do not skip Kubernetes version upgrades beyond two minor versions.",
  "last_verified": "2026-05-08",
  "path": "skills/alibaba/alibaba-ack-container-platform-operator",
  "author": "github: VincentChuWaiChow",
  "version": "0.1.0"
}

SKILL.md 3.1 KB

---
name: alibaba-ack-container-platform-operator
description: Operate 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.
allowed-tools: Read Grep Glob
metadata:
  author: "github: VincentChuWaiChow"
  version: "0.1.0"
  updated: "2026-05-08"
  category: platform
---

# Alibaba Cloud ACK Container Platform Operator

## Purpose

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.

## When to use

Use this skill for:

- ACK cluster type selection: Managed vs. Dedicated vs. Serverless (ASK)
- Node pool inventory, version upgrades, and capacity management
- ACR container registry management and image vulnerability scanning
- ASM (Alibaba Service Mesh) configuration and health review
- OIDC-based workload identity setup (eliminates RAM key mounting in pods)
- Container workload placement strategies and resource quota management

## Lean operating rules

- Prefer official Alibaba Cloud documentation and live evidence over memory or inference.
- Separate confirmed facts from inference. If a cluster state was not verified, say so.
- Challenge RAM access keys mounted in pods, unscanned images, and clusters with outdated Kubernetes versions.
- Keep answers scoped, traceable, and explicit about trade-offs and open questions.
- Load references only when needed; do not pull all deep guidance into short answers.

## Key container platform guidance

- **ACK Managed**: control plane managed by Alibaba Cloud. Most common production choice. Worker nodes remain in customer VPC.
- **ACK Dedicated**: customer manages all control plane components. More flexibility but higher operational burden.
- **ACK Serverless (ASK)**: no worker nodes provisioned. Workloads run on ECI. Best for burst or irregular workloads.
- **ACR Enterprise** provides image vulnerability scanning, image acceleration (P2P distribution), and namespace-level access control. Prefer Enterprise over basic ACR for production.
- **ASM** is Istio-based with Alibaba Cloud extensions. Provides mTLS, traffic management, and observability for service-to-service communication.
- **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.

## References

Load these only when needed:

- [Workflow and output contract](references/workflow-and-output.md) — use when executing the full cluster review or formatting the final operations output.
- [Official sources](references/official-sources.md) — use when grounding Alibaba Cloud ACK/ACR/ASM service behavior or feature claims.

## Response minimum

Return, at minimum:

- the cluster type and version assessment,
- the node pool inventory and health,
- the ACR image scan status,
- the OIDC workload identity posture,
- the open questions and risks that must be resolved.