Quote ingress records from chart into ingress template

[alexellis]

Description

Quote ingress records from chart into ingress template

Why is this needed?

The previous template was too closely tied to the beta version of ingress to work with the new format and layout of ingress v1.

Instead of trying to remap values from custom fields in the values.yaml file, this version quotes the text directly meaning it works better for the newer format.

Who is this for?

New users of OpenFaaS on Kubernetes.

How Has This Been Tested?

Tested e2e with a KinD cluster and inlets.

alex@bq:~$ kubectl get issuer -n openfaas
NAME                  READY   AGE
letsencrypt-prod      True    4m32s
letsencrypt-staging   True    4m32s
alex@bq:~$ kubectl get ingress -n openfaas
NAME               CLASS   HOSTS                            ADDRESS          PORTS     AGE
openfaas-ingress   nginx   gw.d.o6s.io,dashboard.d.o6s.io   134.209.188.10   80, 443   6m54s
alex@bq:~$ kubectl get svc -n default
NAME                                 TYPE           CLUSTER-IP      EXTERNAL-IP                     PORT(S)                      AGE
ingress-nginx-controller             LoadBalancer   10.96.205.130   134.209.188.10,134.209.188.10   80:32019/TCP,443:32205/TCP   27m
ingress-nginx-controller-admission   ClusterIP      10.96.188.19    <none>                          443/TCP                      27m
kubernetes                           ClusterIP      10.96.0.1       <none>                          443/TCP                      30m
alex@bq:~$ 
alex@bq:~$ curl -i https://gw.d.o6s.io
HTTP/2 403 
date: Tue, 28 May 2024 09:26:54 GMT
content-length: 0
strict-transport-security: max-age=31536000; includeSubDomains

alex@bq:~$ curl -i https://dashboard.d.o6s.io
HTTP/2 200 
date: Tue, 28 May 2024 09:26:57 GMT
content-type: text/html
strict-transport-security: max-age=31536000; includeSubDomains

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

For some people this may be a breaking change