Ingress — CloudBeaver

Exposure via Ingress uses a hostname, path, optional TLS, and cert-manager annotations (illustrative example — replace with a domain you control).

Prerequisites

• Ingress Controller (e.g., NGINX).
• Certificate issuance: optional, via cert-manager if using the annotation below.

Example

tdp-cloudbeaver:
  ingress:
    enabled: true
    ingressClassName: "nginx"
    hostname: cloudbeaver.example.com
    path: /
    pathType: Prefix
    tls: true
    annotations:
      cert-manager.io/cluster-issuer: "letsencrypt-prod"

Terminal input

helm upgrade --install <release> \
  oci://registry.tecnisys.com.br/tdp/charts/tdp-cloudbeaver \
  -n <namespace> --create-namespace \
  -f meu-values.yaml

Replace cloudbeaver.example.com and the cluster issuer with the values from your environment.

Access

After the deploy, use the URL corresponding to the hostname (and the https scheme if tls: true).

Troubleshooting

Issue	Cause	Solution
Ingress missing	ingress.enabled: false	Enable in values
Host does not resolve	DNS / local hosts	Adjust DNS or client resolution
TLS fails	Incorrect Issuer / Secret	Check cert-manager and the TLS Secret