Skip to content
This repository was archived by the owner on May 16, 2023. It is now read-only.
This repository was archived by the owner on May 16, 2023. It is now read-only.

[logstash 7.16] Can't set custom ingress port anymore in logstash chart #1500

@nickbabkin

Description

@nickbabkin

Chart version:
7.16.1

Describe the bug:

We use different TCP ports for different inputs on logstash. We expose only handful of them via external ingress.

After 7.16 upgrade, possibility to set custom servicePort for ingress has been removed from logstash chart for unknown reason.

Now, it is automatically set equal to httpPort value in configuration, which does not allow us to expose custom port on ingress anymore and instead forces us to use httpPort setting.

number: {{ $httpPort }}

The change was introduced with this commit:
1459b2f

In other charts, however, it is still possible to use custom servicePort, for example elasticsearch 7.16 chart:

number: {{ .servicePort | default $httpPort }}

Is there any reason for restricting it for logstash?

Thank you.

Metadata

Metadata

Assignees

Labels

bugSomething isn't workinglogstash

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions