Home / BeaverDeck / Docs / Configuration Guide / Networking

Networking, Ports, and Ingress

Permissions: enabling or changing Ingress requires Kubernetes permission to update the Helm release and its Service/Ingress resources. Referencing TLS also requires access to create or use the named TLS Secret according to cluster policy.

The container listens on 8080 by default, and the chart exposes Service port 80 to target port 8080. Health checks use /healthz.

ingress:
            enabled: true
            className: nginx
            host: beaverdeck.example.com
            path: /
            pathType: Prefix
            tls:
              - hosts:
                  - beaverdeck.example.com
                secretName: beaverdeck-tls

When using a non-root path such as /beaverdeck, the ingress controller must forward that same prefix to BeaverDeck because the chart passes ingress.path as BASE_PATH.