Vai al contenuto
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
zhaoxuya520/competition-k8s-control-planeLinux, cloud e container

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 installazioni+3 in 7 giorni44,8K StelleMITsincronizzato 2 ore fa

Installa

Non hai ancora la CLI di NotHoly? Installala prima.

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

Scrive in ⁦~/.notholy/skills⁩ dopo aver controllato la firma e lo SHA-256.

FirmaFirmato, ed25519
JtFIxYG9wl…JgxUrBAw==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Pacchetto6628a028…7b6f643b
6628a0281fb3…750f7b6f643b3 file · ⁦2.1 KB⁩
ScansioneBassonessuna segnalazione
La scansione non ha trovato nulla da segnalare in questa versione.Vedi la scansione completa
Sorgentegithub.com/zhaoxuya520/reverse-skill/tree/main/CTF-Sandbox-Orchestrator/competition-k8s-control-plane@cab634b

Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: 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

File di questa versione

Permessi

PermessoDichiaratoTrovato dalla scansione
Legge fileNoNo
Scrive fileNoNo
Esegue comandi shellNoNo
Usa la reteNoNo
Usa i connettoriNoNo
Controlla un browserNoNo

Segnalazioni della scansione

Rivisto il 13 nov 2026

La scansione non ha trovato nulla da segnalare in questa versione.

Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.

VersionePubblicataCommitSHA-256FirmaCambio di permessi
v2026.9.22-cab634b13 nov 2026cab634b6628a028Firmata–

Chiedi tutto quello che il tuo perimetro consente.

Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.

  1. 1/3

    Crea l'account

    Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.

    PrivatoAzienda
  2. 2/3

    Aggiungi crediti

    Con carta. Paghi a token, senza abbonamento.

    $5.00ricarica minima
  3. 3/3

    Chiedi

    In chat, oppure installa la CLI ed esegui notholy login nel terminale.

    $ notholy login