Skip to content

Bring up a cluster

ConfigHub manages configuration for live infrastructure, so this tutorial starts with infrastructure: a local Kubernetes cluster wired to ConfigHub. Everything else in the tutorial deploys to it.

Set up the cluster with:

cub cluster up --name dev

This one command does two things at once:

  • On your machine: creates a kind cluster named dev, installs Argo CD, and the argobot helper tool into the cluster.
  • In ConfigHub: creates two spaces. dev holds a server-hosted OCI worker and an OCI target named target that represents the cluster. dev-argo-apps holds a root "app of apps" Argo Application unit; every deployment you later add to this cluster gets its own Argo Application here.

The target is how ConfigHub addresses this cluster — later steps refer to it as dev/target. Configuration published for this target is pulled and reconciled by the Argo CD instance running in the cluster. ConfigHub never pushes into your cluster — the cluster pulls from ConfigHub. We'll see that in action shortly.

Check

Load the cluster's credentials into your shell and confirm it's alive:

source ~/.confighub/clusters/dev.env
kubectl get pods -n argocd

You should see the Argo CD pods Running.

Open the ArgoCD web UI

You can open the web UI with this convenient command:

cub cluster open dev

It will open the UI in your browser and copy the admin password to your clipboard (might not work on all OSes). The admin username is "admin". If the clipboard copy didn't work, you will find the admin password in the ARGOCD_PASSWORD environment variable set from the ~/.confighub/clusters/dev.env file.

On the ConfigHub side:

cub space get dev
cub unit list --space dev-argo-apps

The dev space holds the worker and OCI target; its companion dev-argo-apps space contains the root Application unit.

Summary

  • cub cluster up gives you a local cluster that is already wired to ConfigHub: a target to address it by, and Argo CD inside it pulling from ConfigHub's OCI endpoint.
  • Deployment in ConfigHub is pull-based. You publish configuration; the cluster's operator pulls and reconciles it.

Next

Install a Component

Further reading