Terminal
Terminal/Skill
Helps set up a new Konnect Gateway control plane, covering data plane hosting, region, naming, and ownership choices.
By Kong
Works with
npx skills add kong/ai-marketplace --skill konnect-control-plane-bootstrapHelp an operator stand up a new Konnect Gateway control plane with the right bootstrap assumptions before the problem becomes Gateway drift or runtime troubleshooting.
Use this skill for initial setup, first-run topology choices, naming, labels, ownership boundaries, and "what should we create first?" decisions. Do not use it for ongoing incident triage, retrofitting generic Gateway config, or fixing an already unhealthy existing control plane unless the missing piece is still bootstrap scope.
kong-konnect MCP server first for live inspection of
existing control planes, groups, and adjacent Konnect Gateway resources.konnect-gateway-triage instead of treating the problem as bootstrap.terraform-konnect for HCL-managed control planes,
kongctl-declarative for kongctl YAML, and deck-gateway only after the
control plane exists and the task becomes Gateway-entity configuration.kong-konnect MCP is not connected, say so
early and continue with user-provided artifacts or repo context.Load only the reference file that matches the active branch:
references/topology-choice.md
references/bootstrap-artifacts.md
references/ownership-boundaries.md
First determine whether the user is:
If the real problem is health, rollout, connectivity, or config application on
an existing control plane, hand off early to konnect-gateway-triage.
Clarify:
Do not treat a tutorial quickstart as the final production shape by default.
Load references/topology-choice.md when the deployment shape itself is still
the hard part.
Decide:
Bootstrap errors here cause long-lived confusion later, especially when several control planes look similar.
Load references/ownership-boundaries.md when region, labels, names, or team
ownership are the main source of ambiguity.
For a new control plane, keep these concerns distinct:
The control plane is not “done” just because it exists in Konnect.
Load references/bootstrap-artifacts.md when the operator needs the bootstrap
milestones spelled out more explicitly.
Default decision rule:
terraform-konnectkongctl, bootstrap in
kongctl-declarativeDo not force migration between tools during bootstrap unless the user asked for it.
Before calling the bootstrap complete, verify:
Common next steps:
konnect-gateway-triage if the control plane exists but connectivity or
rollout is unhealthydeck-gateway for first Gateway-entity config in a decK repoterraform-konnect or kongctl-declarative for durable control-plane
codificationdecK is not the control-plane bootstrap tool; it becomes relevant after the
control plane exists.Before answering, verify that you can state:
konnect-gateway-triage when the bootstrap is complete enough that the
remaining problem is health, connectivity, or rollout.terraform-konnect or kongctl-declarative when the user wants the
control plane managed as code.deck-gateway once the control plane exists and the task becomes Gateway
entity configuration.