[bitnami/logstash] Can't create NodePort through logstash helm chart

[joshua-heidrich]

Name and Version

bitnami/logstash 5.1.15

What architecture are you using?

amd64

What steps will reproduce the bug?

1. Installing Logstash through Helm-Chart with service.type=NodePort

Are you using any custom parameters or values?

service:
  type: NodePort
  ports:
    - name: gelf
      port: 1234
      targetPort: 1234
      nodePort: 30345
      protocol: UDP

What is the expected behavior?

The install works.

What do you see instead?

Error: UPGRADE FAILED: failed to create resource: Service "logstash-headless" is invalid: spec.ports[0].nodePort: Forbidden: may not be used when type is 'ClusterIP'

Additional information

I think I already have the source of the problem. There is this section in headless-svc.yaml:

spec:
  type: ClusterIP
  clusterIP: None
  ports:
    {{- include "common.tplvalues.render" (dict "value" .Values.service.ports "context" $) | nindent 4 }}
  selector: {{ include "common.labels.matchLabels" . | nindent 4 }}

It uses .Values.service.ports which I have defined as follows:

    - name: gelf
      port: 1234
      targetPort: 1234
      nodePort: 30345
      protocol: UDP

I need the "nodePort"-part because I want to create a Nodeport. But this uses the NodePort port to create a ClusterIP which obviously does not work.

[javsalgar]

Hi!

Thank you so much for reporting! I believe we could use the omit go template function to not add the nodePort section inside the headless service. I will forward this to the team. However, if you want to speed up the process, would you like to submit a PR?

[github-actions]

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

[github-actions]

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.

[copy1dollar]

This issue is not yet resolved.
The same problem is happening with 5.4.4.

related : elastic/helm-charts#839

[github-actions]

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

[github-actions]

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.