OpenParable
Skip to content
← Back to skills

K8S Platform Change

DevOps & Security
k8s-platform-change

K8S Platform Change is an Agent Skill for devops & security published in the vllm-project/semantic-router repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Modifies Kubernetes-facing operator, CRD, deployment-profile, or DSL translation behavior for semantic-router platform integration. Use when changing operator APIs or controllers, deployment stack manifests, profile-owned platform wiring, or router-to-Kubernetes translation layers.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/vllm-project/semantic-router/blob/HEAD/tools/agent/skills/k8s-platform-change/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/k8s-platform-change, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Kubernetes Platform Change

Trigger

  • Change operator APIs, CRDs, or controller-facing config translation
  • Change deployment-profile manifests or profile-owned platform wiring under deploy/kubernetes/**
  • Change router-to-Kubernetes DSL translation or config bridging layers

Workflow

  1. Read change surfaces, module boundaries, and testing strategy for the affected Kubernetes-facing surface
  2. Modify the operator, deployment profile, or DSL translation behavior
  3. Run make agent-report ENV=cpu CHANGED_FILES="..." to identify impacted surfaces and affected profile coverage
  4. Run make agent-ci-gate CHANGED_FILES="..." to validate the affected constraints
  5. Verify control-plane behavior, stack-manifest behavior, and DSL translation still describe the same platform contract

Gotchas

  • Do not hide control-plane and stack-resource differences; they can change in the same loop, but they should remain explicit in the final report.
  • Manifest-only edits still need profile-aware validation when they change response-api, authz, observability, or routing stack behavior.
  • Router config representation debt belongs to config-platform-change; Kubernetes-facing translation and deployment ownership belong here.

Must Read

Standard Commands

  • make agent-report ENV=cpu CHANGED_FILES="..."
  • make agent-ci-gate CHANGED_FILES="..."
  • make agent-feature-gate ENV=cpu CHANGED_FILES="..."

Acceptance

  • Operator APIs, DSL translation, deployment manifests, and affected Kubernetes validation paths stay aligned
  • Profile-owned resources and control-plane behavior remain explicit even when they change in the same loop