We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
the problem lies when you want to deploy logstash next to elastic like this:
..... elastic values here...
eck-logstash: enabled: true version: 8.15.3 count: 1 elasticsearchRefs: - name: elasticsearch clusterName: eck pipelinesRef: secretName: "logstash-pipeline-secret" services: - name: beats service: spec: type: LoadBalancer ports: - port: 5044 name: "beats" protocol: TCP targetPort: 5044 - name: tcp service: spec: type: LoadBalancer ports: - port: 50000 name: "tcp" protocol: TCP targetPort: 50000
this will result in conflict and it will refuse to deploy saying that piplines and piplinesref cant be together at the same time
in my example it isnt
but because the way that values file for the nested logstash chart , it seems that it only overrides available values like the pipleinsref i have
and because pipline:[] is in the default values file , it will make the conflict
a fast fix is to download the charts locally and comment out the piplines:[] line in the nested logstah chart
The text was updated successfully, but these errors were encountered:
It appears to be a duplicate of #8000, which has already been resolved via #8087. The fix will be included in the upcoming ECK release (v2.15.0).
Sorry, something went wrong.
No branches or pull requests
the problem lies when you want to deploy logstash next to elastic like this:
..... elastic values here...
eck-logstash:
enabled: true
version: 8.15.3
count: 1
elasticsearchRefs:
- name: elasticsearch
clusterName: eck
pipelinesRef:
secretName: "logstash-pipeline-secret"
services:
- name: beats
service:
spec:
type: LoadBalancer
ports:
- port: 5044
name: "beats"
protocol: TCP
targetPort: 5044
- name: tcp
service:
spec:
type: LoadBalancer
ports:
- port: 50000
name: "tcp"
protocol: TCP
targetPort: 50000
this will result in conflict and it will refuse to deploy saying that piplines and piplinesref cant be together at the same time
in my example it isnt
but because the way that values file for the nested logstash chart , it seems that it only overrides available values like the pipleinsref i have
and because pipline:[] is in the default values file , it will make the conflict
a fast fix is to download the charts locally and comment out the piplines:[] line in the nested logstah chart
The text was updated successfully, but these errors were encountered: