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
Is your feature request related to a problem? Please describe.
The fluent-operator always creates hostPath volumes for the fluentbit daemonsets. Additional volumes are only appended.
We use k8s-as-a-service and our provider does not allow creating pods with hostPath volumes. But we can mount the node logs via a given persistentVolume (ReadOnlyMany).
We would like to add more flexibility to the volume handling. For example to use persistentVolumeClaim instead of hostPath.
Describe the solution you'd like
This could be done by either a feature toggle to disable the hostPath volumes (varlibcontainers, varlogs, systemd) or switch to persistentVolumeClaim.
Or by overwriting all volumes with the ones in the FluentBit CR.
@OlegVanHorst You still want to deploy fluentbit as a DaemonSet, but each pod mount the same ReadOnlyMany?
In that case, you may need a toggle to disable hostPath options and enable ROM persistentVolumeClaim at the same time.
You're welcome to create a PR for this
Is your feature request related to a problem? Please describe.
The fluent-operator always creates hostPath volumes for the fluentbit daemonsets. Additional volumes are only appended.
We use k8s-as-a-service and our provider does not allow creating pods with hostPath volumes. But we can mount the node logs via a given persistentVolume (ReadOnlyMany).
We would like to add more flexibility to the volume handling. For example to use persistentVolumeClaim instead of hostPath.
Describe the solution you'd like
This could be done by either a feature toggle to disable the hostPath volumes (varlibcontainers, varlogs, systemd) or switch to persistentVolumeClaim.
Or by overwriting all volumes with the ones in the FluentBit CR.
Additional context
PersistentVolume to mount host logs:
The text was updated successfully, but these errors were encountered: