signadot-local

Signadot Local Development

Help the user connect their local machine to a Kubernetes cluster, run workloads locally that participate in cluster traffic, override sandbox traffic, and record/inspect traffic. If the user specifies a command ($ARGUMENTS), focus on that section.

Important: This skill covers two separate CLI subcommands:

• signadot local — connect, proxy, override, status, disconnect
• signadot traffic — record and inspect sandbox traffic (does NOT require signadot local connect)

For traffic recording/inspection, go directly to signadot traffic record or signadot traffic inspect. Do not use signadot local for traffic operations.

Overview

Signadot local development enables developers to:

1. Run a service on their laptop that receives real cluster traffic
2. Access cluster services (DNS, networking) from local code
3. Intercept and override specific sandbox traffic with a local implementation
4. Record and inspect HTTP/gRPC traffic flowing through sandboxes

Prerequisites

• Signadot CLI installed and authenticated (signadot auth status)
• Signadot Operator installed in the target cluster
• Local configuration in ~/.signadot/config.yaml (for local connect). Use --config to switch between config files:

local:
  connections:
  - cluster: <cluster-name>       # from Signadot dashboard
    kubeContext: <kube-context>    # from your kubeconfig

# Use a specific config for a different cluster/org
signadot --config ~/configs/staging.yaml local connect --cluster staging

Connection Types

Configure in ~/.signadot/config.yaml under each connection:

• PortForward (default): Uses kubectl port-forwarding. Requires kubeContext.
• ControlPlaneProxy: Routes through Signadot control plane. No kubectl access needed. Add type: ControlPlaneProxy.
• ProxyAddress: For exposed SOCKS5 proxy (e.g. VPN). Add type: ProxyAddress and proxyAddress: <host>:<port>.

# ControlPlaneProxy — simplest setup, no kubectl required
local:
  connections:
  - cluster: staging
    type: ControlPlaneProxy