Skip to content
This repository has been archived by the owner on Jan 24, 2023. It is now read-only.

Kubernetes Ingress certificate is incorrectly set #4005

Closed
2 of 9 tasks
miro-grapeup opened this issue Nov 4, 2019 · 1 comment
Closed
2 of 9 tasks

Kubernetes Ingress certificate is incorrectly set #4005

miro-grapeup opened this issue Nov 4, 2019 · 1 comment
Labels
backlog community Community Raised Issue

Comments

@miro-grapeup
Copy link

miro-grapeup commented Nov 4, 2019

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

There should be no problem when using ingress configuration.

Actual behaviour

There is an error that ingress cannot find proper secret for tls connection

Steps to reproduce the behavior

Use similar configuration:

console:
  service:
    ingress:
      enabled: true
      host: stratos.example.com

Log output covering before error and any error statements

time="2019-11-04T21:54:37Z" level=error msg="Error configuring TLS for ingress console/stratos-console-ingress: secret console/{{ .Release.Name }}-ingress-tls does not exist"
time="2019-11-04T21:54:38Z" level=error msg="Error configuring TLS for ingress console/stratos-console-ingress: secret console/{{ .Release.Name }}-ingress-tls does not exist"
time="2019-11-04T21:54:39Z" level=error msg="Error configuring TLS for ingress console/stratos-console-ingress: secret console/{{ .Release.Name }}-ingress-tls does not exist"
time="2019-11-04T21:54:40Z" level=error msg="Error configuring TLS for ingress console/stratos-console-ingress: secret console/{{ .Release.Name }}-ingress-tls does not exist"
time="2019-11-04T21:54:41Z" level=error msg="Error configuring TLS for ingress console/stratos-console-ingress: secret console/{{ .Release.Name }}-ingress-tls does not exist"

Detailed Description

The problem is with duplicated inner curly braces here:

- secretName: {{ default "{{ .Release.Name }}-ingress-tls" .Values.console.service.ingress.secretName | quote }}

Context

This breaks an ingress functionality

Possible Implementation

Remove duplicate braces from here:

- secretName: {{ default "{{ .Release.Name }}-ingress-tls" .Values.console.service.ingress.secretName | quote }}

@troytop
Copy link

troytop commented Nov 26, 2019

Was going to open a similar bug. If possible, this should behave like suse/scf or kubecf does when automatically creating ingresses.

@nwmac nwmac added the backlog label Nov 27, 2019
@nwmac nwmac mentioned this issue Nov 27, 2019
@richard-cox richard-cox added the community Community Raised Issue label Dec 12, 2019
@nwmac nwmac closed this as completed Feb 26, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
backlog community Community Raised Issue
Projects
None yet
Development

No branches or pull requests

4 participants