Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[kibana/elasticsearch] ingress defined with hosts breaks other ingress with nginx

See original GitHub issue

What I would like to suggest is to have support through values configuration for non-hosts definition when deploying kibana (or elasticsearch).

Chart version:

version: 5.0.11
appVersion: 7.6.1

Kubernetes version:

Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.3", GitCommit:"06ad960bfd03b39c8310aaf92d1e7c12ce618213", GitTreeState:"clean", BuildDate:"2020-02-11T18:14:22Z", GoVersion:"go1.13.6", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.3", GitCommit:"06ad960bfd03b39c8310aaf92d1e7c12ce618213", GitTreeState:"clean", BuildDate:"2020-02-11T18:07:13Z", GoVersion:"go1.13.6", Compiler:"gc", Platform:"linux/amd64"}

Kubernetes provider: E.g. GKE (Google Kubernetes Engine) Local deployment

Helm Version:

version.BuildInfo{Version:"v3.1.1", GitCommit:"afe70585407b420d0097d07b21c47dc511525ac8", GitTreeState:"clean", GoVersion:"go1.13.8"}

Describe the bug:

When creating an ingress with hosts, it makes all others ingress with default “*” to be not accessible. I have seen this behaviour with nginx-ingress (stable/nginx-ingress from https://helm.nginx.co/stable appVersion: 1.6.3)

Steps to reproduce:

helm install nginx-ingress stable/nginx-ingress
helm install kibana elastic/kibana --set ingress.enabled=true --set ingress.hosts[0]=test.com

Expected behavior:

I expect that all the ingress should be working regardless

Any additional context: I understand that this issue comes from nginx, but I also believe that it has less impact by updating the helm chart here.