Run any Skill in Manus with one click

k8s-platform-change

Stars4,986

Forks758

UpdatedMay 30, 2026 at 11:49

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

vllm-project

vllm-project/semantic-router

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	k8s-platform-change
category	primary
description	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.

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

Read change surfaces, module boundaries, and testing strategy for the affected Kubernetes-facing surface
Modify the operator, deployment profile, or DSL translation behavior
Run make agent-report ENV=cpu CHANGED_FILES="..." to identify impacted surfaces and affected profile coverage
Run make agent-ci-gate CHANGED_FILES="..." to validate the affected constraints
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

More from this repository

same repository

openclaw-vsr-bridge

vllm-project/semantic-router

Install vLLM Semantic Router in agent-safe mode, import supported OpenClaw model providers into canonical VSR config, and rewrite OpenClaw to target VSR.

2026-07-135.0k

vllm-semantic-router-harness

vllm-project/semantic-router

Bridges native skill discovery into the vLLM Semantic Router repository harness, routing tasks through the canonical agent-report flow, repo-local skill registry, and validation commands. Use when starting any task inside the vLLM Semantic Router repository to resolve the correct primary skill, read canonical docs, and run harness validation.

2026-05-305.0k

config-platform-change

vllm-project/semantic-router

Synchronizes config representations across router config, Python CLI schema, and dashboard config UI. Use when adding or changing a config concept that spans those surfaces or addressing config representation debt before Kubernetes-facing translation.

2026-05-305.0k

maintainer-issue-pr-management

vllm-project/semantic-router

Manages GitHub issue and pull-request lifecycle including creation, updates, triage labelling, and closeout metadata using canonical templates and repository taxonomy. Use when a maintainer asks to create, update, close, or triage GitHub issues or PRs, or when issue creation requires codebase analysis for scope, labels, or acceptance criteria.

2026-05-305.0k

maintainer-release-ops

vllm-project/semantic-router

Maintainer release and milestone operating workflow. Use when a maintainer wants to plan a release, create milestone issues, sync GitHub issue or PR state, generate a daily review brief, or manage stale PRs and backlog routing.

2026-05-305.0k

routing-calibration-loop

vllm-project/semantic-router

Calibrates routing changes against a live router endpoint with executable probes, local DSL validation, versioned deploys, and structured failure review. Use when tuning signals, projections, decisions, or maintained route examples against a real apiserver.

2026-05-305.0k

name	k8s-platform-change
category	primary
description	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.

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

Read change surfaces, module boundaries, and testing strategy for the affected Kubernetes-facing surface
Modify the operator, deployment profile, or DSL translation behavior
Run make agent-report ENV=cpu CHANGED_FILES="..." to identify impacted surfaces and affected profile coverage
Run make agent-ci-gate CHANGED_FILES="..." to validate the affected constraints
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