tencentblueking/bk-cli · Archived

bk-cli-bcs

当需要通过 `bk-cli bcs` 调用 BCS API 时使用;当前主要覆盖 `bk-cli bcs cluster_manager` 下的集群、节点、节点组、节点模板、任务、模板?

First seen Jul 1, 2026

Installation

$ npx skills add tencentblueking/bk-cli --skill bk-cli-bcs

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Also in this package

Other skills from tencentblueking/bk-cli · top by installs.

npx skills add tencentblueking/bk-cli

Browse all from tencentblueking/bk-cli

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 5
License LICENSE.txt
Default branch master
Open issues 6
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 4,254 B
  • docs SUMMARY.md 224 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 7 installs

SKILL.md

bk-cli bcs

用于让 Agent 通过 bk-cli bcs 调用 BCS API。开始前先读取 ../bk-cli-shared/SKILL.md,共享 skill 负责认证、context、tenant、stage、dry-run、verbose、header/body 等通用调用规则。

当前可用命令层级:

bk-cli bcs cluster_manager <action>

如果用户要操作其他 BCS 模块,先运行 bk-cli bcs -h 查看是否已有对应 subsystem。

Action 清单

cluster_manager 当前包含:

  • 集群:createcluster、importcluster、update_cluster
  • 弹性伸缩:updateautoscalingoption、updateautoscalingstatus
  • 节点:deletenodesfromcluster、batchdeletenodesfromcluster、addnodestoclusterv2、addsubnettocluster、updatenodeannotations、checknodeincluster、cordonnode、drainnode、checkdrainnode、updatenodelabels、updatenodetaints、uncordon_node
  • 节点组:createnodegroup、updatenodegroup、disablenodegroupautoscale、enablenodegroupautoscale、updategroupminmaxsize、updategroupdesirednode、updategroupdesiredsize、cleannodesingroup、cleannodesingroup_v2
  • 节点模板:createnodetemplate、updatenodetemplate、transnodegrouptonode_template
  • 任务与配置:retrytask、skiptask、createtemplateconfig、deletetemplateconfig、updatevirtualcluster_quota

调用步骤

  1. 找 action:

``bash bk-cli bcs cluster_manager -h ``

  1. 看目标 action 的默认帮助。默认 -h 会展示 Usage、Examples、flags,以及是否有 body schema:

``bash bk-cli bcs clustermanager createcluster -h ``

  1. 如果默认帮助提示可查看 body schema,用 -h --body-schema 查看完整 request body schema:

``bash bk-cli bcs clustermanager createcluster -h --body-schema ``

  1. 按 Examples 构造命令。复杂请求体统一通过 --body '<json>' 传入,不要猜 body 字段。
  2. 首次执行或写操作前先加 --dry-run,确认 request.url、request.params、request.body、request.headers。

输入规则

  • 路径参数和 query 参数是普通 flags,例如 --clusterID、--nodeGroupID、--nodes、--isForce=true。
  • DELETE action 的 query string 也用 flags 传入。
  • 有些写操作要求 --body;缺失时会返回 missing_param 和 required parameter --body is missing。
  • -h --body-schema 只显示 schema,不执行请求。

常用示例

更新集群:

bk-cli bcs cluster_manager update_cluster \
  --clusterID BCS-K8S-12345 \
  --body '{"clusterID":"BCS-K8S-12345"}'

下架集群节点:

bk-cli bcs cluster_manager delete_nodes_from_cluster \
  --clusterID BCS-K8S-12345 \
  --nodes 10.0.0.1,10.0.0.2 \
  --deleteMode terminate \
  --isForce=true \
  --operator admin

创建节点组:

bk-cli bcs cluster_manager create_node_group -h
bk-cli bcs cluster_manager create_node_group -h --body-schema

bk-cli bcs cluster_manager create_node_group \
  --body '{"name":"node-group","clusterID":"BCS-K8S-12345","region":"ap-guangzhou","autoScaling":{"vpcID":"vpc-id","zones":["ap-guangzhou-1"],"maxSize":1},"launchTemplate":{"CPU":1,"GPU":0,"Mem":1},"creator":"admin","nodeOS":"linux"}'

回收节点组节点 V2:

bk-cli bcs cluster_manager clean_nodes_in_group_v2 \
  --nodeGroupID node-group-id \
  --clusterID BCS-K8S-12345 \
  --nodes 10.0.0.1,10.0.0.2 \
  --operator admin

排障

  • missing_param:检查是否缺少必填 flag,例如 --clusterID、--nodeGroupID、--projectID、--body。
  • required parameter --body is missing:先运行该 action 的 -h,按 Examples 补 --body '<json>'。
  • body JSON 解析失败:把 JSON 压成一行,或用脚本生成合法 JSON 后再传给 --body。
  • 不确定 body 字段:运行 bk-cli bcs cluster_manager <action> -h --body-schema。
  • 请求不符合预期:加 --dry-run 检查最终请求。