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

Sonarqube broken template when using ingress #324

Open
sashokbg opened this issue Jan 6, 2022 · 1 comment
Open

Sonarqube broken template when using ingress #324

sashokbg opened this issue Jan 6, 2022 · 1 comment

Comments

@sashokbg
Copy link

sashokbg commented Jan 6, 2022

This is a bug report

How to reproduce:
helm template -f sonar-gke/files/helm_values.yaml wb-sonar oteemocharts/sonarqube

What works:
helm template -f sonar-gke/files/helm_values.yaml wb-sonar oteemocharts/sonarqube --version 9.4.1
It looks like the problem was introduced in 9.5.0

Error message:

Error: template: sonarqube/templates/ingress.yaml:31:41: executing "sonarqube/templates/ingress.yaml" at <.serviceName>: can't evaluate field serviceName in type interface {}

Use --debug flag to render out invalid YAML

Values

replicaCount: 1

image:
  tag: latest

ingress:
  enabled: true
  hosts:
    - name: "sonar.mydomain.com"
      path: "/*"
  annotations:
    kubernetes.io/ingress.class: "gce"
    kubernetes.io/ingress.allow-http: "true"
    kubernetes.io/ingress.global-static-ip-name: "sonar-global-address"

postgresql:
  enabled: true
  postgresqlUsername: "sonar"
  postgresqlPassword: "pass"
  postgresqlDatabase: "db"
  service:
    port: 5432

@olivierboudet
Copy link

I can confirm this issue.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants