Saltar al contenido
Nuevo

DeepSeek V4.1 Flash gratis por 7 días: 10M tokens al día tras una recarga de $10 o más. Hasta el 30/11.

Cómo funciona
zhaoxuya520/competition-k8s-control-planeLinux, cloud y contenedores

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 instalaciones+3 en 7 días44,8 mil EstrellasMITsincronizado hace 2 horas

Instalar

¿Aún no tienes la CLI de NotHoly? Instálala primero.

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

Escribe en ⁦~/.notholy/skills⁩ después de comprobar la firma y el SHA-256.

FirmaFirmado, ed25519
JtFIxYG9wl…JgxUrBAw==La CLI comprueba el SHA-256 y la firma antes de escribir cualquier archivo.
Paquete6628a028…7b6f643b
6628a0281fb3…750f7b6f643b3 archivos · ⁦2.1 KB⁩
EscaneoBajosin hallazgos
El escaneo no encontró nada que señalar en esta versión.Ver el escaneo completo
Fuentegithub.com/zhaoxuya520/reverse-skill/tree/main/CTF-Sandbox-Orchestrator/competition-k8s-control-plane@cab634b

Esta entrada todavía no está escrita en tu idioma, así que aparece en 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

Archivos de esta versión

Permisos

PermisoDeclaradoHallado en el escaneo
Lee archivosNoNo
Escribe archivosNoNo
Ejecuta comandos de shellNoNo
Usa la redNoNo
Usa conectoresNoNo
Controla un navegadorNoNo

Hallazgos del escaneo

Revisado el 13 nov 2026

El escaneo no encontró nada que señalar en esta versión.

Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.

VersiónPublicadaCommitSHA-256FirmaCambio de permisos
v2026.9.22-cab634b13 nov 2026cab634b6628a028Firmada–

Pregunta todo lo que tu alcance permite.

Crea la cuenta, añade créditos y haz la primera pregunta en el chat o en la terminal.

  1. 1/3

    Crea la cuenta

    Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.

    IndividualEmpresa
  2. 2/3

    Añade créditos

    Con tarjeta. Pagas por token, sin suscripción.

    $5.00recarga mínima
  3. 3/3

    Pregunta

    En el chat, o instala el CLI y ejecuta notholy login en tu terminal.

    $ notholy login