Merge pull request #2031 from NCEAS/feature-1954-k8s-ingress-defaultbackend

add configurable ingress defaultBackend for arcticdata.io wordpress s…

Author: artntek

helm/templates/ingress.yaml

@@ -42,6 +42,10 @@ metadata:
       {{ . | nindent 6 }}
     {{- end }}
 spec:
+  {{- if .Values.ingress.defaultBackend.enabled }}
+  defaultBackend:
+  {{- omit .Values.ingress.defaultBackend "enabled" | toYaml | nindent 4 }}
+  {{- end }}
   ingressClassName: {{ .Values.ingress.className }}
   {{- if .Values.ingress.tls }}
   tls:

helm/values.yaml

@@ -718,6 +718,21 @@ ingress:
     # https://nginx.org/en/docs/http/ngx_http_core_module.html#client_max_body_size
     nginx.ingress.kubernetes.io/client_max_body_size: "10m"
 
+  ## @param ingress.defaultBackend (optional) default for any requests not matching defined paths
+  ## If none of the hosts or paths match the HTTP request in the Ingress objects, the traffic is
+  ## routed to your default backend. Not typically required, unless metacatui
+  ## Content included here under `defaultBackend` will be added to the ingress definition under
+  ## `spec.defaultBackend'; for example:
+  ##
+  ##   spec:
+  ##     defaultBackend:
+  ##       service:
+  ##         name: myrelease-wordpress
+  ##         port:
+  ##           number: 80
+  ##
+  defaultBackend: []
+
   ## @param ingress.rewriteRules rewrite rules for the nginx ingress
   ## These rules will be added to the section
   ## metadata: