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

[filebeat|metricbeat] Override probes commands #420

Merged
merged 2 commits into from
Dec 27, 2019

Conversation

jmlrt
Copy link
Member

@jmlrt jmlrt commented Dec 27, 2019

Some outputs can't be tested using filebeat test output or metricbeat test output commands.

Having these commands hardcoded in ReadinessProbe prevent to use Filebeat / Metricbeat with outputs which haven't implemented the test command.

Fix #316 and #325

@jmlrt jmlrt added the bug Something isn't working label Dec 27, 2019
@jmlrt jmlrt self-assigned this Dec 27, 2019
@jmlrt jmlrt marked this pull request as ready for review December 27, 2019 14:42
@jmlrt jmlrt requested review from Crazybus and a team December 27, 2019 14:42
Copy link
Contributor

@Crazybus Crazybus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

FYI it would have already been possible to override the values for the sections which already had {{ toYaml .Values.readinessProbe | indent 10 }}. Since the hardcoded part is specified first anything added to .Values.readinessProbe would have overridden the hardcoded part. This way is much more obvious and cleaner though of course!

@jmlrt jmlrt merged commit 1ae7c76 into elastic:master Dec 27, 2019
@jmlrt jmlrt deleted the override-probe branch December 27, 2019 15:29
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Filebeat: Readiness probe failed: kafka output doesn't support testing
2 participants