You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 16, 2023. It is now read-only.
Describe the feature:
Introduce a new key kind into the values.yaml which is set to DaemonSet by default, but can be set to Deployment instead - so the application runs as a Deployment.
Describe a specific use case for the feature:
I have a use case where I need to run only a single instance of Filebeat, which would tail a single file in a specific location in a PVC. For a such use case, it would be good to have this feature (similar to what fluent-bit does).
The text was updated successfully, but these errors were encountered:
utkuozdemir
changed the title
Allow running as Deployment as an anternative to DaemonSet
[filebeat] Allow running as Deployment as an anternative to DaemonSet
Nov 24, 2020
Describe the feature:
Introduce a new key
kind
into thevalues.yaml
which is set toDaemonSet
by default, but can be set toDeployment
instead - so the application runs as a Deployment.Describe a specific use case for the feature:
I have a use case where I need to run only a single instance of Filebeat, which would tail a single file in a specific location in a PVC. For a such use case, it would be good to have this feature (similar to what fluent-bit does).
The text was updated successfully, but these errors were encountered: