Skip to content

README.md

Latest commit

 

History

History
66 lines (40 loc) · 2.02 KB

README.md

File metadata and controls

66 lines (40 loc) · 2.02 KB

Part 2: Deploy a Zarf Package

In Part 1, you built a Zarf package for ArgoCD. In this part, you'll deploy that package to your local Kubernetes cluster and access the ArgoCD dashboard.

Make sure you're in the same zarf-package directory you used in Part 1.

Step 1: Inspect the Environment

Confirm the package tarball from Part 1 is present:

ls

You should see a file like zarf-package-argocd-amd64-9.4.4.tar.zst. The architecture may be different depending on your local machine.

Also verify your cluster is reachable:

zarf tools kubectl cluster-info

Step 2: Deploy the Package

Run the deploy command:

zarf package deploy zarf-package-argocd-amd64-9.4.4.tar.zst

Zarf will prompt you to select the package (if multiple are present) and confirm each component before deploying. Accept the defaults to proceed.

Once deployment completes, verify the ArgoCD resources are running:

zarf tools kubectl get all -n argocd

You should see the pods, services, deployments, and replica sets that make up the ArgoCD Helm chart.

Step 3: Retrieve the ArgoCD admin password

Before we access the ArgoCD Dashboard, we need to retrieve the automatically generated admin password:

zarf tools kubectl -n argocd get secret argocd-initial-admin-secret \
          -o jsonpath="{.data.password}" | base64 -d; echo

Step 4: Access the ArgoCD Dashboard

Note

If you completed the Zarf Connect Service section in Part 1, you can use zarf connect argocd as a shorthand for the port-forward command below.

Zarf is designed for environments with limited connectivity, so the ArgoCD service isn't exposed externally by default. Use kubectl to set up a port forward:

zarf tools kubectl port-forward -n argocd service/argocd-server 42000:80

Then open your browser to http://localhost:42000.

Back: Part 1: Create a Zarf Package | Next: Part 3: Inspect a Zarf Package