Home / BeaverDeck / Docs / Configuration Guide / Helm install

Kubernetes and Helm Install

This guide is for DevOps engineers, platform administrators, and developers who install or operate BeaverDeck. It is based on the reviewed application repository, Helm chart, Dockerfile, runtime config, and UI code.

Permissions: the Helm operator must be allowed to create or update the namespaced workload resources and the chart's cluster-scoped ClusterRole and ClusterRoleBinding. Runtime user permissions are documented separately in the application permission matrix.

Install the official chart from the GHCR OCI registry. The chart creates a Deployment, Service, ServiceAccount, cluster-scoped RBAC, suppressed Insights ConfigMap, and optional Ingress.

helm upgrade --install beaverdeck oci://ghcr.io/arequs/charts/beaverdeck \
            --namespace beaverdeck \
            --create-namespace \
            --set clusterName=your-cluster-name

If ingress is disabled, port-forward the Service and open http://localhost:8080.

kubectl -n beaverdeck port-forward svc/beaverdeck 8080:80

On first start, if the auth configuration Secret is missing, BeaverDeck shows an initialization screen and asks for the initial admin username and password.