Kong/ai-marketplace / plugins/kong-konnect/skills/konnect-control-plane-bootstrap
konnect-control-plane-bootstrap
VerifiedBootstrap new Konnect Gateway control planes. Use for first-run topology, hosted versus self-hosted data planes, region/name/ownership choices, or moving from quickstart setup to durable management. Not for runtime triage or post-bootstrap Gateway config.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.9 KB |
| references/bootstrap-artifacts.md | markdown | 2.0 KB |
| references/ownership-boundaries.md | markdown | 2.0 KB |
| references/topology-choice.md | markdown | 2.1 KB |
references/ownership-boundaries.md
View on GitHub# Ownership Boundaries
Use this file when naming, labels, region, repo ownership, or durable
management path are the real bootstrap questions.
## Core Rule
Bootstrap boundaries become long-lived operational boundaries. Treat them as
first-class decisions, not as afterthoughts.
## Boundary Questions
- which region should own this control plane
- how will names distinguish environment or purpose
- which labels or slices separate ownership
- which repo and automation path will manage the control plane
- which tool owns durable config: Terraform or `kongctl`
## Decision Rules
- Prefer names that encode environment or purpose clearly enough to avoid
operators debugging the wrong control plane later.
- Prefer labels or slices that match the actual operating boundary, not just
the bootstrap requestor.
- Choose the durable tool from existing repo ownership first. Do not introduce
Terraform or `kongctl` as a new default during bootstrap unless the user asks
for that migration.
- Treat region as an explicit design choice. If the region is ambiguous, do not
paper over it with a generic "create first, fix later" answer.
## Common Risks
| Risk | Why it matters |
|---|---|
| Region chosen casually | later symptoms look like auth or drift issues |
| Similar control plane names | operators debug the wrong environment |
| No explicit owner | bootstrap succeeds but durable management is unclear |
## What To Check Before Moving On
- whether the control plane can still be identified unambiguously once several
environments exist
- whether the repo or automation owner is named explicitly
- whether the recommended toolchain matches the files the team already keeps in
version control
- whether the boundary decision resolves the user's real ambiguity instead of
deferring it
## What To Return
Return:
- the intended ownership boundary
- the durable management path
- the specific naming, region, or ownership rule that should be kept stable
- the specific bootstrap decision that must be fixed before moving on
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |