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

[aitorhh]

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:

1. helm install nginx-ingress stable/nginx-ingress
2. 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.

[botelastic[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[aitorhh]

Unless it has been solved in another issues or PR, I believe it's something quite relevant that shouldn't be closed.

[botelastic[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[jmlrt]

still valid

[botelastic[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[jmlrt]

still valid

[botelastic[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[jmlrt]

still valid

[botelastic[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[jmlrt]

still valid

[ghost]

anyone facing issue with kibana ingress? {"statusCode":400,"error":"Bad Request","message":"Invalid cookie header"}

linode kubernetes cluster

[botelastic[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[jmlrt]

still valid

[botelastic[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[botelastic[bot]]

This issue has been automatically closed because it has not had recent activity since being marked as stale.

[botelastic[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[tormachris]

still valid

[DmitryZakharov]

Please make it work. We now deploy our own ingress object instead and set ingress.enabled: false

[DmitryZakharov]

One could take an idea from grafana, which does exactly what is needed https://artifacthub.io/packages/helm/grafana/grafana/6.1.10?modal=template&template=ingress.yaml

[botelastic[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[DmitryZakharov]

Please don't close it. Is there any plan to have it fixed ?

[botelastic[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.