kubekanvas connect

Establish a persistent connection to the KubeKanvas server and listen for real-time deployment commands. This is the command that bridges the visual Kubernetes IDE to your local clusters.

Usage

kubekanvas connect [options]

Options

Flag	Description
`-d, --debug`	Enable debug output for troubleshooting connection issues
`-v, --verbose`	Enable verbose output showing all incoming messages

Prerequisites

You must be logged in (kubekanvas login)
You must have at least one cluster configured (kubekanvas configure)

How It Works

The CLI authenticates with the server using your stored credentials
Establishes a persistent connection to the KubeKanvas server
Enters a listening loop, processing incoming deployment commands
Each command is routed to the appropriate handler for Helm operations

Supported Operations

The CLI processes the following deployment operations received from the KubeKanvas IDE:

Install a new Helm release on the target cluster
Upgrade an existing release to a new version
Rollback a release to a previous revision
Remove a Helm release from the cluster
Retrieve the current status of a release

Example

kubekanvas connect

kubekanvas connect --debug

Example Output

$ kubekanvas connect
🔌 Connected to KubeKanvas server
📡 Listening for deployment commands...
   Press Ctrl+C to disconnect

🚀 Received: Install project "my-app" on cluster "dev-cluster"
   Installing Helm chart to namespace "default"...
✅ Release "my-app" installed successfully

Graceful Shutdown

Press Ctrl+C to stop the listener. The CLI performs a clean disconnect from the server before exiting.

Running as a Background Service

For production environments, you may want to run the CLI as a persistent background process:

nohup kubekanvas connect > /var/log/kubekanvas.log 2>&1 &

[Unit]
Description=KubeKanvas CLI Agent
After=network.target

[Service]
Type=simple
User=kubekanvas
ExecStart=/usr/local/bin/kubekanvas connect
Restart=always
RestartSec=10

[Install]
WantedBy=multi-user.target

Tip: Use kubekanvas list-clusters to verify which clusters are registered before connecting.