Templating issues with ingress

[jezravina91]

Steps to replicate:

Defined ingress configuration based on documentation.

Tested with the following configuration:

` ingress:
enabled: true
labels: {}
# traffic: external
annotations: |-
certmanager.k8s.io/cluster-issuer: letsencrypt-prod
kubernetes.io/ingress.class: nginx
kubernetes.io/tls-acme: "true"

hosts:
  - host: vault.dev.coinspectapp.com
    paths:
      - backend:
        serviceName: dev-vault
        servicePort: 8200`

Also the following:
`paths:

• backend:
  serviceName:
  servicePort: `

paths: []

Working:
paths: - ""

Expected:

• Should work as per documentation

Actual:

• errors were encountered.

Error:
Ingress.extensions "dev-vault" is invalid: spec.rules[0].http.paths[0].path: Invalid value: "map[backend: serviceName:dev-vault servicePort:8200]": must be an absolute path

Manifest:

Vault is installed using helm with the following tar file:

• https://github.com/hashicorp/vault-helm/archive/v0.5.0.tar.gz

I am not an expert, this could just be all my fault.
I just tried to follow the documentation.

Thanks!

[nohaj]

My configuration :

  ingress:
    enabled: true
    hosts:
      - host: vault.mydomain.com
    tls:
       - hosts:
         - vault.mydomain.com
         secretName: vault

Was not working with the 0.5.0 version of the chart but it works with the master branch of the ingress template.

Thanks to jaredallard (7568cb1)

[tvoran]

Hi @Nitro2003, indeed it looks like the documentation for the ingress values is a little out of date, sorry about that. The paths list in Values.server.ingress.hosts[] should just be a list of path strings, since the chart template already defines the backend stanza:

vault-helm/templates/server-ingress.yaml

Lines 35 to 41 in 2a37c57

	paths:
	{{- range .paths }}
	- path: {{ . }}
	backend:
	serviceName: {{ $serviceName }}
	servicePort: {{ $servicePort }}
	{{- end }}

So I think in your case, you'd want something like this set in the values:

    hosts:
      - host: vault.dev.coinspectapp.com
        paths:
          - /

(In the upcoming release the paths list defaults to ['/'], so that's why the master branch behaves a little differently. We'll get the docs fixed too.)

[tvoran]

The documentation has been updated, so I'm going to close this for now. Let us know if you run into other issues.

[jezravina91]

Thanks for the quick update!