首页龙虾技能列表 › Kubernetes Skills — 技能工具

Kubernetes Skills — 技能工具

v1.0.0

[自动翻译] Manage multiple Kubernetes clusters, switch contexts, and perform cross-cluster operations. Use when working with multiple clusters, comparing environ...

2· 2,209·8 当前·8 累计·💬 5
by @rohitg00·MIT-0
下载技能包
License
MIT-0
最后更新
2026/4/9
安全扫描
VirusTotal
可疑
查看报告
OpenClaw
可疑
medium confidence
The instructions align with multi-cluster Kubernetes tasks, but the skill references reading kubeconfigs and syncing secrets while declaring no credential or config requirements and has no verifiable source — that mismatch is a significant concern.
评估建议
This skill appears to be a legitimate multi-cluster Kubernetes helper, but take these precautions before installing or using it: - Verify provenance: the skill's source and homepage are unknown; prefer skills from trusted publishers. - Expect it needs access to kubeconfig files or cluster credentials even though it doesn't declare them. Do not expose production kubeconfigs or long-lived admin tokens to untrusted skills or agents. - Secret-sync examples show the agent reading secrets in one clus...
详细分析 ▾
用途与能力
The skill's name, description, and runtime instructions consistently target multi-cluster Kubernetes management (context switching, CAPI, Helm, GitOps, secret sync). That capability set is coherent with the stated purpose.
指令范围
SKILL.md instructs the agent to view/sanitize kubeconfigs (kubeconfig_view()), list contexts, read secrets from a source cluster and apply them to targets, and to obtain workload kubeconfigs via CAPI tools. Those instructions implicitly require access to kubeconfig files and cluster credentials and perform sensitive actions (secret synchronization, cross-cluster writes). The skill does not constrain or document how sensitive data will be handled or where it may be transmitted.
安装机制
Instruction-only skill with no install spec and no code files — nothing will be downloaded or written by the skill itself. This minimizes supply-chain/installation risk.
凭证需求
The skill declares no required env vars, credentials, or config paths, yet the instructions rely on kubeconfigs (examples use export KUBECONFIG and kubeconfig_view()) and service-account patterns. There is a mismatch between declared requirements (none) and the obvious need for cluster credentials and kubeconfig files to perform the described operations.
持久化与权限
The skill is not always-enabled and is user-invocable. It does not request persistent presence or modify other skills. Autonomous invocation is enabled (default) but not, by itself, a red flag here.
安全有层次,运行前请审查代码。

License

MIT-0

可自由使用、修改和再分发,无需署名。

运行时依赖

无特殊依赖

版本

latestv1.0.02026/1/26

- Initial release of k8s-multicluster skill for managing multiple Kubernetes clusters. - Provides context management: list, view, and switch between cluster contexts. - Supports cross-cluster operations for resources, comparisons, and parallel queries. - Includes Cluster API (CAPI) management: list clusters, get details, manage machines, and scale deployments. - Enables multi-cluster Helm and GitOps workflows with Flux and ArgoCD. - Documents federation and cross-cluster patterns (e.g., secret sync, service discovery). - Shares best practices and links to related skills for cluster troubleshooting and GitOps.

● 可疑

安装命令 点击复制

官方npx clawhub@latest install k8-multicluster
镜像加速npx clawhub@latest install k8-multicluster --registry https://cn.clawhub-mirror.com

技能文档

Cross-cluster operations and context management using kubectl-mcp-server's multi-cluster support.

Context Management

List Available Contexts

list_contexts_tool()

View Current Context

kubeconfig_view()  # Shows sanitized kubeconfig

Switch Context

CLI: kubectl-mcp-server context

Cross-Cluster Operations

All kubectl-mcp-server tools support the context parameter:

# Get pods from production cluster
get_pods(namespace="default", context="production-cluster")

# Get pods from staging cluster get_pods(namespace="default", context="staging-cluster")

Common Multi-Cluster Patterns

Compare Environments

# Compare deployment across clusters
compare_namespaces(
    namespace1="production",
    namespace2="staging",
    resource_type="deployment",
    context="production-cluster"
)

Parallel Queries

Query multiple clusters simultaneously:

# Production cluster
get_pods(namespace="app", context="prod-us-east")
get_pods(namespace="app", context="prod-eu-west")

# Development cluster get_pods(namespace="app", context="development")

Cross-Cluster Health Check

# Check all clusters
for context in ["prod-1", "prod-2", "staging"]:
    get_nodes(context=context)
    get_pods(namespace="kube-system", context=context)

Cluster API (CAPI) Management

For managing cluster lifecycle:

List Managed Clusters

capi_clusters_list_tool(namespace="capi-system")

Get Cluster Details

capi_cluster_get_tool(name="prod-cluster", namespace="capi-system")

Get Workload Cluster Kubeconfig

capi_cluster_kubeconfig_tool(name="prod-cluster", namespace="capi-system")

Machine Management

capi_machines_list_tool(namespace="capi-system")
capi_machinedeployments_list_tool(namespace="capi-system")

Scale Cluster

capi_machinedeployment_scale_tool(
    name="prod-cluster-md-0",
    namespace="capi-system",
    replicas=5
)

See CONTEXT-SWITCHING.md for detailed patterns.

Multi-Cluster Helm

Deploy charts to specific clusters:

install_helm_chart(
    name="nginx",
    chart="bitnami/nginx",
    namespace="web",
    context="production-cluster"
)

list_helm_releases( namespace="web", context="staging-cluster" )

Multi-Cluster GitOps

Flux Across Clusters

flux_kustomizations_list_tool(
    namespace="flux-system",
    context="cluster-1"
)

flux_reconcile_tool( kind="kustomization", name="apps", namespace="flux-system", context="cluster-2" )

ArgoCD Across Clusters

argocd_apps_list_tool(namespace="argocd", context="management-cluster")

Federation Patterns

Secret Synchronization

# Read from source cluster
get_secrets(namespace="app", context="source-cluster")

# Apply to target cluster (via manifest) apply_manifest(secret_manifest, namespace="app", context="target-cluster")

Cross-Cluster Service Discovery

With Cilium ClusterMesh or Istio multi-cluster:
cilium_nodes_list_tool(context="cluster-1")
istio_proxy_status_tool(context="cluster-2")

Best Practices

  • Naming Convention: Use descriptive context names
- prod-us-east-1, staging-eu-west-1

  • Access Control: Different kubeconfigs per environment
- Prod: Read-only for most users - Dev: Full access for developers

  • Always Specify Context: Avoid accidental cross-cluster operations
   # Explicit is better
   get_pods(namespace="app", context="production")
   
  • Cluster Groups: Organize by purpose
- Production: prod- - Staging: staging- - Development: dev-*

Related Skills

数据来源:ClawHub ↗ · 中文优化:龙虾技能库
OpenClaw 技能定制 / 插件定制 / 私有工作流定制

免费技能或插件可能存在安全风险,如需更匹配、更安全的方案,建议联系付费定制

了解定制服务