Add conditional TLS support to Helm chart Ingress

[NicolasBoulard]

Describe the solution you'd like

I would like to enhance the Helm chart by adding support for TLS configuration in the Ingress resource. This would allow users to define TLS settings directly via Helm values when deploying pgAdmin4 with Ingress enabled.

The proposed addition would look like this:

{{- if .Values.ingress.enabled }}
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: {{ template "pgadmin4.fullname" . }}
  {{- with .Values.commonLabels }}
  labels: {{ . | toYaml | nindent 4 }}
  {{- end }}
  {{- if or .Values.ingress.annotations .Values.commonAnnotations }}
  annotations: {{ merge .Values.ingress.annotations .Values.commonAnnotations | toYaml | nindent 4 }}
  {{- end }}
spec:
  rules:
  - host: {{ tpl .Values.ingress.hostname . }}
    http:
      paths:
      - backend:
          service:
            name: {{ template "pgadmin4.fullname" . }}
            port:
              name: http
        path: /
        pathType: Prefix
  {{- if .Values.ingress.tlsSecret }}
  tls:
  - hosts:
    - {{ tpl .Values.ingress.hostname . }}
    secretName: {{ .Values.ingress.tlsSecret }}
  {{- end }}
{{- end }}

Describe alternatives you've considered

Manually patching the Ingress after Helm deployment.

Additional context

This feature would improve security and flexibility for users deploying pgAdmin4 in Kubernetes environments. I am willing to submit a Pull Request to implement this enhancement if the maintainers agree.