Skip to content

Path 1 — Cloud Default Image

Deploy a blueprint to a cloud Kubernetes cluster using the Hopr pre-built image from the GitLab registry. No Docker build required.

When to use

  • Quick trial deployment to a cloud cluster
  • Evaluating a blueprint before customizing Section 1
  • Production deployment where the default application logic is sufficient

Prerequisites

  • kubectl configured with your target cluster context
  • Kubernetes cluster with LoadBalancer service support (GKE, EKS, AKS, or MetalLB)
  • Valid Hopr license (trial or commercial)
  • Blueprint ZIP bundle downloaded with credentials pre-injected

Fill the registry secrets

Path 1 uses two image pull secrets, both pre-configured in the ZIP:

  • hopr-registrycreds — authorizes pulling the WoSP sidecar image from the Hopr GitLab registry
  • app-registrycreds — authorizes pulling the default application image

These secrets are already in each pod's 02-secrets.yaml with your credentials. Verify they are filled before deploying:

grep -A2 "hopr-registrycreds\|app-registrycreds" gateway/02-secrets.yaml

Both entries should have non-empty data: values.

Deploy

bash deploy.sh

deploy.sh applies manifests in the correct order across all pod namespaces. Let it complete before verifying.

Verify

Check pod readiness

kubectl get pods -A

Wait for all blueprint pods to show 3/3 Ready. On first deployment, image pulls may take 1–2 minutes.

LoadBalancer IP assignment takes time

On cloud providers, LoadBalancer services take 2–5 minutes to receive an external IP. If EXTERNAL-IP shows <pending>, wait and check again: 

kubectl get svc -A --watch

Confirm auto-trigger

kubectl logs -n <blueprint>-gateway-ns deployment/gateway -c web-app -f

Expected: 🔁 Auto-trigger complete — 5/5 messages sent.

Check delivery at the sink

kubectl port-forward -n <blueprint>-sink-ns deployment/sink 8000:8000
curl http://localhost:8000/output

Expected: {"count": 5, "results": [...]}

Infrastructure cost

Each blueprint pod that uses a LoadBalancer service type incurs a cloud infrastructure charge of approximately $16–20/month per LoadBalancer, depending on provider and region. Run bash teardown.sh when not in active use to avoid unnecessary charges.

Teardown

bash teardown.sh