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/topology-choice.md
View on GitHub# Topology Choice
Use this file when the main bootstrap decision is what kind of environment is
being built.
## Core Rule
Separate quick proof-of-life from durable environment design. A local or guided
quickstart is not automatically the right shared operating model.
## Questions To Clarify
- is this a local proof-of-capability or a long-lived team environment
- are data planes self-hosted, Dedicated Cloud Gateways, or another managed
hosting shape
- is this dev, staging, prod, or a shared platform slice
- does the team need one control plane now or a repeatable pattern for several
environments soon
## Common Decision Patterns
| Situation | Default interpretation |
|---|---|
| Tutorial or first-time setup | quickstart plus later durable codification |
| Shared team environment | explicit region, ownership, and durable toolchain from the start |
| Production bootstrap | avoid treating quickstart defaults as final architecture |
## Decision Rules
- Prefer a quickstart framing only when the operator mainly needs proof that
Konnect Gateway can come up at all.
- Prefer a durable environment framing when the same control plane name,
region, or ownership decision will be reused by a team or pipeline.
- Treat hosted versus self-hosted data planes as an operating-model choice, not
just a provisioning detail. It changes what must be proven next.
- If the user is already discussing rollout health, attachment failures, or
config application on an existing control plane, this is no longer a
topology-choice question. Hand off to `konnect-gateway-triage`.
## What To Check Before Recommending A Shape
- whether the user needs local speed or repeatable team ownership
- whether the region is constrained by org policy or adjacent services
- whether the next step after creation is data plane attachment, managed
provisioning, or repository codification
- whether the recommendation still works once a second environment is added
## What To Return
Return:
- the intended topology shape
- whether the current path is quickstart-only or durable
- the data plane hosting model that should be assumed next
- which next skill or tool should own codification
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 |