multi-branch-cluster-setup

Create isolated minikube clusters and devspace contexts for parallel Ark branches.

6|Updated Nov 21, 2025

Search Tags:#kubernetes #git worktree #minikube #devspace #ark #cluster setup #port forwarding

Ready to run

npx skills add https://github.com/remiverdiesen/ark-fork --skill multi-branch-cluster-setup

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: multi-branch-cluster-setup
Source: https://github.com/remiverdiesen/ark-fork/tree/main/.claude/skills/multi-branch-cluster-setup
Command: npx skills add https://github.com/remiverdiesen/ark-fork --skill multi-branch-cluster-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires minikube, kubectl, helm, devspace, docker, jq, nc, and includes scripts (resource) components.

What problem does it solve?

This Skill removes the manual coordination needed to run multiple Ark branches at the same time, each with its own isolated Kubernetes cluster and devspace context.

Core Features & Use Cases

Per-branch isolation: Creates one minikube cluster for each branch so parallel work does not interfere across worktrees.
Automated deployment flow: Sets up clusters, binds devspace contexts, deploys the first cluster, transfers images, and deploys the rest.
Port management: Starts and stops branch-specific port-forwards with predictable dashboard, API, and gateway ports.
Use case: A team working on three feature branches can bring up three separate local environments and test them side by side without manual cluster juggling.

Quick Start

Ask me to set up isolated Ark clusters for the branches you want, then deploy the first cluster, transfer images, and start port-forwards.

Frequently Asked Questions about multi-branch-cluster-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I set up isolated Kubernetes clusters for parallel Git branch development?▼

To set up isolated Kubernetes clusters for parallel Git branch development, you use minikube and devspace to create a dedicated cluster per Git worktree. This ensures branch-specific deployments run simultaneously without interfering with each other.

How does devspace integrate with minikube for branch-specific deployments?▼

Devspace integrates with minikube for branch-specific deployments by binding a unique devspace context to each cluster. This allows automated deployment flows to target specific branches and transfer images between isolated local environments.

What's the best way to manage port forwarding across multiple local minikube clusters?▼

The best way to manage port forwarding across multiple local minikube clusters is using scripted deployment commands. This assigns predictable dashboard, API, and gateway ports dynamically, preventing collisions when testing branches side by side.

Do I need kubectl and helm installed to run multiple devspace contexts simultaneously?▼

Yes, you need kubectl and helm installed to run multiple devspace contexts simultaneously. The cluster setup also requires docker, jq, and nc to manage deterministic cluster naming, image transfers, and network port assignments.

Can I test multiple feature branches side by side without manual cluster juggling?▼

Yes, you can test multiple feature branches side by side without manual cluster juggling. The automated workflow creates separate local environments for each branch, deploys the first cluster, transfers images, and configures the remaining deployments.

Why does simultaneous multi-branch testing require deterministic cluster naming?▼

Simultaneous multi-branch testing requires deterministic cluster naming to maintain strict per-branch isolation. Predictable names ensure devspace contexts, image transfers, and port-forwards bind to the correct local Kubernetes environment without conflicts.