Feat: Support Dedicated Cloud Gateways resources (declarative & imperative)

[rspurgeon]

https://developer.konghq.com/api/konnect/cloud-gateways/v2/

[github-actions]

🎯 Agentic Issue Triage

Summary: This is a feature request to add full support for [Dedicated Cloud Gateways]((developer.konghq.com/redacted) resources in kongctl — covering both imperative (CLI commands) and declarative (config-as-code) workflows.

Currently, the codebase has partial Cloud Gateway integration: a --is-cloud-gateway boolean flag on create control-plane and a cloud_gateway field in the declarative control plane schema. The dedicated Cloud Gateways v2 API resources (networks, configurations, custom domains, transit gateways, etc.) are not yet addressable as first-class kongctl resources.

📦 Current State of Cloud Gateway Support

Existing cloud gateway code lives in:

• internal/cmd/root/products/konnect/gateway/controlplane/createControlPlane.go — --is-cloud-gateway flag
• internal/declarative/executor/control_plane_adapter.go — cloud_gateway field handling
• internal/declarative/planner/control_plane_planner.go — planner-side cloud gateway diffing

The [Cloud Gateways v2 API]((developer.konghq.com/redacted) exposes additional resources not yet represented in kongctl, such as:

• Cloud Gateway Networks
• Cloud Gateway Configurations
• Custom Domains
• Transit Gateways

🗂️ Suggested Sub-Tasks / Checklist

Imperative (CLI commands):

• kongctl get cloud-gateway-networks — list/get networks
• kongctl create cloud-gateway-network — provision a network
• kongctl delete cloud-gateway-network — deprovision
• kongctl get cloud-gateway-configurations — list/get configs
• kongctl create/update cloud-gateway-configuration
• Additional resources per v2 API (transit gateways, custom domains, etc.)

Declarative:

• Add cloud_gateway_networks and related resource types to the declarative schema (internal/declarative/resources/)
• Implement planners for each new resource type (internal/declarative/planner/)
• Implement executors/adapters (internal/declarative/executor/)
• Wire new resource types into the declarative config loader and validator

SDK / HTTP client:

• Check if the Konnect Go SDK already covers Cloud Gateways v2 — if so, use it; otherwise, add the necessary client methods to internal/konnect/

Tests:

• Unit tests for new planners and executors
• Integration tests for API interactions
• E2E scenarios under test/e2e/scenarios/

🔧 Implementation Notes & Patterns to Follow

The existing control plane resource is the best reference implementation:

1. Resource type — internal/declarative/resources/control_plane.go
2. Planner — internal/declarative/planner/control_plane_planner.go
3. Executor/adapter — internal/declarative/executor/control_plane_adapter.go
4. CLI command — internal/cmd/root/products/konnect/gateway/controlplane/

Follow the verb-noun command pattern: kongctl (verb) cloud-gateway-(resource).

Check the Konnect SDK for existing Cloud Gateways v2 bindings before writing raw HTTP calls:

grep -r "CloudGateway\|cloud_gateway" $(go env GOPATH)/pkg/mod/github.com/\!kong/sdk-konnect-go*/

📚 Relevant Resources

• [Konnect Cloud Gateways v2 API Reference]((developer.konghq.com/redacted)
• [Kong Konnect Dedicated Cloud Gateways docs]((docs.konghq.com/redacted)
• sdk-konnect-go — check for existing Cloud Gateway client coverage
• Existing control plane declarative implementation as a reference pattern

Generated by Opened Issue Triage for issue #509

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/issue-triage.md@69b5e3ae5fa7f35fa555b0a22aee14c36ab57ebb