Deployment

Every blueprint supports three deployment paths. Choose the one that matches your environment and goals.

• Path 0 — Local k3d: Build images locally, import into k3d, no external registry required. Best for development, CI, and first-time deployment.
• Path 1 — Cloud, Default Image: Use the Hopr pre-built image from the GitLab registry. Requires hopr-registrycreds and app-registrycreds secrets. Best for a quick cloud trial.
• Path 2 — Cloud, Custom Image: Modify Section 1 in app.py, rebuild your image, push to your registry, deploy with your image. Best for production with custom business logic.

The deploy.sh script handles manifest ordering, namespace creation, and pod readiness checks automatically. You do not need to run kubectl apply manually — deploy.sh does it in the correct sequence with the correct flags.

In this section

• Path 0 — Local k3d — single- and multi-cluster local deployment with troubleshooting guide
• Path 1 — Cloud Default Image — cloud deployment using the Hopr pre-built image
• Path 2 — Cloud Custom Image — deploy with your customized application image
• Multi-Cluster Guide — cross-cluster networking, deploy ordering, and k3d port mappings