Pular para o conteúdo
Novo

DeepSeek V4.1 Flash grátis por 7 dias: 10M tokens por dia após recarga de $10 ou mais. Até 30/11.

Como funciona
zhaoxuya520/competition-k8s-control-planeLinux, cloud e containers

competition-k8s-control-plane

⁨Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for Kubernetes API analysis, service-account trust, RBAC edges, admission and controller behavior, cluster secrets, workload mutation, and namespace-scoped drift. Use when the user asks to inspect kube API permissions, serv⁩

v2026.9.22-cab634b3 instalações+3 em 7 dias44,8 mil EstrelasMITsincronizado há 2 horas

Instalar

Ainda não tem a CLI da NotHoly? Instale primeiro.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install zhaoxuya520/competition-k8s-control-plane

Grava em ⁦~/.notholy/skills⁩ depois de conferir a assinatura e o SHA-256.

AssinaturaAssinado, ed25519
JtFIxYG9wl…JgxUrBAw==A CLI confere o SHA-256 e a assinatura antes de gravar qualquer arquivo.
Pacote6628a028…7b6f643b
6628a0281fb3…750f7b6f643b3 arquivos · ⁦2.1 KB⁩
VarreduraBaixonenhum achado
A varredura não encontrou nada para apontar nesta versão.Ver a varredura completa
Fontegithub.com/zhaoxuya520/reverse-skill/tree/main/CTF-Sandbox-Orchestrator/competition-k8s-control-plane@cab634b

Este item ainda não foi escrito no seu idioma, então aparece em English.

Use this skill only as a downstream specialization after $ctf-sandbox-orchestrator is already active and has established sandbox assumptions, node ownership, and evidence priorities. If that has not happened yet, return to $ctf-sandbox-orchestrator first.

Use this skill when the decisive path runs through Kubernetes control-plane state, API permissions, or controller behavior rather than a single container's runtime alone.

Reply in Simplified Chinese unless the user explicitly requests English.

Quick Start

  1. Separate manifest intent from live cluster state: API objects, mutations, controllers, secrets, and resulting workloads.
  2. Identify the active principal first: service account, kubeconfig identity, node credential, webhook, or controller.
  3. Map the smallest control-plane edge to its workload effect.
  4. Keep RBAC, service accounts, owner references, namespace boundaries, and secret consumers in compact evidence blocks.
  5. Reproduce the smallest cluster action that yields the decisive workload or secret effect.

Workflow

1. Map The API Trust Path

  • Record namespaces, service accounts, Roles, ClusterRoles, bindings, admission hooks, controllers, and the resources they can mutate.
  • Distinguish read access, create access, patch access, exec access, and secret access.
  • Keep principal, verb, resource, namespace, and resulting object in one chain.

2. Trace Mutation To Workload State

  • Show how an API action becomes a pod, volume mount, secret exposure, env injection, job run, or controller-created artifact.
  • Compare checked-in YAML against live objects after defaulting, admission mutation, or controller reconciliation.
  • Distinguish pod-runtime behavior from cluster-level mutation logic.

3. Reduce To The Decisive Cluster Path

  • Compress the result to the smallest chain: principal -> API permission -> mutated object -> resulting workload, secret, or route effect.
  • Keep kube objects, live describes, and consumed secret or config paths tied to the same namespace and controller.
  • If the problem narrows down to one container's mount or runtime deviation, switch back to the tighter container-runtime skill.

Read This Reference

  • Load references/k8s-control-plane.md for the RBAC checklist, controller checklist, and evidence packaging.
  • If the hard part is metadata-service reachability, workload identity, instance credentials, or metadata-derived privilege, prefer $competition-cloud-metadata-path.

What To Preserve

  • Namespace, service account, verb, resource kind, RoleBinding or ClusterRoleBinding, and owner reference chains
  • Admission mutations, generated workloads, mounted secrets, and controller-produced drift
  • The exact API action or object diff that creates the decisive effect

Arquivos desta versão

Permissões

PermissãoDeclaradaEncontrada na varredura
Lê arquivosNãoNão
Grava arquivosNãoNão
Roda comandos no shellNãoNão
Usa a redeNãoNão
Usa conectoresNãoNão
Controla um navegadorNãoNão

Achados da varredura

Revisado em 13 de nov. de 2026

A varredura não encontrou nada para apontar nesta versão.

Uma varredura limpa reduz o risco, mas não prova que o pacote é seguro. Leia o que você instala.

VersãoPublicada emCommitSHA-256AssinaturaMudança de permissão
v2026.9.22-cab634b13 de nov. de 2026cab634b6628a028Assinada–

Pergunte tudo o que o seu escopo permite.

Crie a conta, adicione créditos e faça a primeira pergunta no chat ou no terminal.

  1. 1/3

    Crie a conta

    Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.

    Pessoa físicaEmpresa
  2. 2/3

    Adicione créditos

    No cartão. Você paga por token, sem assinatura.

    $5.00recarga mínima
  3. 3/3

    Pergunte

    No chat, ou instale o CLI e rode notholy login no terminal.

    $ notholy login