This repository has been archived by the owner on May 16, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
[logstash] Unable to install Logstash with configured nodePort #807
Comments
Hi @Gagarmel, Good catch, I didn't test it with IMO we should be able to remove totally helm-charts/logstash/templates/service-headless.yaml Lines 19 to 21 in 6ddd3e3
|
jmlrt
added a commit
to jmlrt/helm-charts
that referenced
this issue
Oct 14, 2020
This commit fix an issue introduced in 8ed75a9 where helm install/upgrade is failing if a NodePort service is defined (see [0] for more details). Logstash headless service used to manage Statefulset does not anymore include `.Values.service.ports` and include only Logstash httpPort. This is done because headless service `ports` doesn't accept `nodePort` values that can be included in `.Values.service.ports` when adding a NodePort service. [0]: elastic#807
jmlrt
added a commit
to jmlrt/helm-charts
that referenced
this issue
Oct 14, 2020
This commit fix an issue introduced in 8ed75a9 where helm install/upgrade is failing if a NodePort service is defined (see [0] for more details). Logstash headless service used to manage Statefulset does not anymore include `.Values.service.ports` and include only Logstash httpPort. This is done because headless service `ports` doesn't accept `nodePort` values that can be included in `.Values.service.ports` when adding a NodePort service. [0]: elastic#807
jmlrt
added a commit
that referenced
this issue
Oct 14, 2020
This commit fix an issue introduced in 8ed75a9 where helm install/upgrade is failing if a NodePort service is defined (see [0] for more details). Logstash headless service used to manage Statefulset does not anymore include `.Values.service.ports` and include only Logstash httpPort. This is done because headless service `ports` doesn't accept `nodePort` values that can be included in `.Values.service.ports` when adding a NodePort service. [0]: #807
jmlrt
added a commit
that referenced
this issue
Oct 16, 2020
This commit fix an issue introduced in 8ed75a9 where helm install/upgrade is failing if a NodePort service is defined (see [0] for more details). Logstash headless service used to manage Statefulset does not anymore include `.Values.service.ports` and include only Logstash httpPort. This is done because headless service `ports` doesn't accept `nodePort` values that can be included in `.Values.service.ports` when adding a NodePort service. [0]: #807
jmlrt
added a commit
that referenced
this issue
Oct 16, 2020
This commit fix an issue introduced in 8ed75a9 where helm install/upgrade is failing if a NodePort service is defined (see [0] for more details). Logstash headless service used to manage Statefulset does not anymore include `.Values.service.ports` and include only Logstash httpPort. This is done because headless service `ports` doesn't accept `nodePort` values that can be included in `.Values.service.ports` when adding a NodePort service. [0]: #807
jmlrt
added a commit
that referenced
this issue
Oct 16, 2020
This commit fix an issue introduced in 8ed75a9 where helm install/upgrade is failing if a NodePort service is defined (see [0] for more details). Logstash headless service used to manage Statefulset does not anymore include `.Values.service.ports` and include only Logstash httpPort. This is done because headless service `ports` doesn't accept `nodePort` values that can be included in `.Values.service.ports` when adding a NodePort service. [0]: #807
galina-tochilkin
pushed a commit
to mtp-devops/3d-party-helm
that referenced
this issue
Dec 20, 2022
This commit fix an issue introduced in 88ea6b7 where helm install/upgrade is failing if a NodePort service is defined (see [0] for more details). Logstash headless service used to manage Statefulset does not anymore include `.Values.service.ports` and include only Logstash httpPort. This is done because headless service `ports` doesn't accept `nodePort` values that can be included in `.Values.service.ports` when adding a NodePort service. [0]: elastic/helm-charts#807
galina-tochilkin
pushed a commit
to mtp-devops/3d-party-helm
that referenced
this issue
Dec 20, 2022
This commit fix an issue introduced in 8ed75a9 where helm install/upgrade is failing if a NodePort service is defined (see [0] for more details). Logstash headless service used to manage Statefulset does not anymore include `.Values.service.ports` and include only Logstash httpPort. This is done because headless service `ports` doesn't accept `nodePort` values that can be included in `.Values.service.ports` when adding a NodePort service. [0]: elastic/helm-charts#807
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Chart version:
7.9.1
Kubernetes version:
v1.15.12
Kubernetes provider: E.g. GKE (Google Kubernetes Engine)
Own
Helm Version:
3.3.0
Provided values.yaml
Describe the bug:
Due to changes made in #776 it is not possible to install a Logstash instance which has a configured
nodePort
.Steps to reproduce:
values.yaml
helm install logstash elastic/logstash -f values.yaml
Expected behavior:
It should be possible to create a Logstash installation with Service
type=NodePort
and configurednodePort=xxxxx
. This was possible in previous versions of this chart.Provide logs and/or server output (if relevant):
Be careful to obfuscate every secrets (credentials, token, public IP, ...) that could be visible in the output before copy-pasting
Any additional context:
The text was updated successfully, but these errors were encountered: