菜单
Set up Canonical k8s and register it as a Juju cloud inside the sandbox VM. Use when asked to set up a k8s substrate, prepare for Kubernetes charm deployments, or before bootstrapping a Juju k8s controller.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/canonical/charm-integration-testing --skill setup-k8s命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Charm Override Investigator - investigates charm metadata and creates per-charm override YAML files in static/charm-overrides/. USE FOR: creating a new override from scratch, updating after an upstream PR lands, fixing broken constraints, auditing against live metadata, recording expected resource inconsistencies (e.g. a retained PVC) so the resource tracker does not flag them. GUIDED WORKFLOWS: write_new_override, update_existing_override, validate_override, write_resource_inconsistency_override. INPUTS: charm name, optional upstream PR URL, optional track filter. OUTPUTS: PR-ready YAML with evidence comments.
Develop a new Juju charm integration validator from scratch. Use when asked to create, write, or build a new validator for an interface.
Review a pull request, address inline reviewer comments, post replies, and apply fixes. Use when asked to review PR feedback, respond to comments, or fix issues raised in a PR.
基于 SOC 职业分类
正在显示 SKILL.md
| name | setup-k8s |
| description | Set up Canonical k8s and register it as a Juju cloud inside the sandbox VM. Use when asked to set up a k8s substrate, prepare for Kubernetes charm deployments, or before bootstrapping a Juju k8s controller. |
Install and configure Canonical k8s inside the sandbox VM and register it as a Juju cloud so that a Juju controller can be bootstrapped against it.
Run the setup script:
$PROJECT_ROOT/development-sandbox/bin/setup-k8s.sh
This is idempotent. Each step checks whether it has already been done. Wait for it to complete before proceeding.
Bootstrap a Juju controller. Use a descriptive controller name:
juju bootstrap local-k8s k8s-ctrl
Create a working model:
juju add-model testing
Verify the substrate is ready:
juju status -m testing
kubectl is not available directly; use sudo k8s kubectl instead./home/ubuntu/k8s.yaml. Set KUBECONFIG=/home/ubuntu/k8s.yaml
if Juju commands need it explicitly.local-k8s Juju cloud name is used by convention. Use it when bootstrapping.wait-ready can take several minutes on first run.