Generated Ingress certificates during Kubernetes deployment are empty

[miro-grapeup]

Frontend Deployment type

• Cloud Foundry Application (cf push)
• Kubernetes, using a helm chart
• Docker, single container deploying all components
• npm run start
• Other (please specify below)

Backend (Jet Stream) Deployment type

• Cloud Foundry Application (cf push)
• Kubernetes, using a helm chart
• Docker, single container deploying all components
• Other (please specify below)

Expected behaviour

The auto generated certificates should be correct

Actual behaviour

Generated Ingress certificates during deployment on k8s are empty

Steps to reproduce the behavior

Use the ingress config similar to scenario in here #4005 but after stratos is deployed you have to manually edit the ingress: kubectl edit ingress $RELEASE_NAME-ingress and fix the incorrect secretName.

Log output covering before error and any error statements

time="2019-11-04T21:58:15Z" level=error msg="Error configuring TLS for ingress console/stratos-console-ingress: secret console/stratos-console-ingress-tls contains the following empty TLS data entries: tls.crt, tls.key"
time="2019-11-04T21:58:16Z" level=error msg="Error configuring TLS for ingress console/stratos-console-ingress: secret console/stratos-console-ingress-tls contains the following empty TLS data entries: tls.crt, tls.key"
time="2019-11-04T21:58:17Z" level=error msg="Error configuring TLS for ingress console/stratos-console-ingress: secret console/stratos-console-ingress-tls contains the following empty TLS data entries: tls.crt, tls.key"

Detailed Description

The below lines have default empty values.

stratos/deploy/kubernetes/console/templates/ingress.yaml

Lines 24 to 25 in dfd39c9

	tls.crt: {{ .Values.console.service.ingress.tls.crt | default "" | b64enc | quote }}
	tls.key: {{ .Values.console.service.ingress.tls.key | default "" | b64enc | quote }}

Context

Possible Implementation

This can be fixed to not use empty default values but to generate certificates or the documentation should be fixed and not saying that by default certs will be generated for ingress.