fluent-bit Support managed identity for Azure Blob output

In addition to shared key authorization for Azure Blob output, it would be nice to be able to use managed identities in environments that support this, such as Azure Kubernetes Service. Managed identities makes it easier to manage fine grained access, and to avoid having secrets that need to be rotated.

Nov 27 '20 10:11 nilsga

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

Mar 06 '21 02:03 github-actions[bot]

This issue was closed because it has been stalled for 5 days with no activity.

Mar 11 '21 02:03 github-actions[bot]

Although this has been inactive, I think it is still valid.

Mar 12 '21 08:03 nilsga

Agreed this is still valid and looks like it is required if you are building managed applications that also need to have logging enabled without manually updating credentials when they are expired. Does this require any attention from the Microsoft side to move forward?

Mar 29 '21 16:03 david-yu

We also have this issue. Is there a possibility that this will be implemented in the future ?

Jun 30 '21 13:06 OpzekerIT

Also have this issue

Feb 16 '22 17:02 michelefa1988

+1

Apr 23 '22 06:04 jrcast

~For anyone looking for a solution, as a workaround, you can use the CSI Blob Driver for Azure. See: https://github.com/kubernetes-sigs/blob-csi-driver~

~You can authenticate the blob driver using an Azure Identity, mount the blob in the FluentBit pod as a PVC, and use the "file" FluentBit output pointed to the corresponding volume path. Note: The CSI driver stores files in the PVC as block blobs.~

EDIT: TLDR; After playing with this idea for a bit, I believe this is not a good solution after all.

fluentBit's file output does not have a way to control how big the files are before rotation. In addition, the CSI Blob driver does not support append blobs or immutable block blobs. So you have to chose between dropping millions of small block blobs or having a large block blob that has to be re-uploaded on every update by fluentBit.

In the end, neither of these 2 options are viable as a workaround.

Apr 26 '22 08:04 jrcast

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days. Maintainers can add the exempt-stale label.

Aug 03 '22 02:08 github-actions[bot]

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days. Maintainers can add the exempt-stale label.

Nov 02 '22 02:11 github-actions[bot]

This issue was closed because it has been stalled for 5 days with no activity.

Nov 08 '22 02:11 github-actions[bot]

Can we stop making this as stale?