Azure Event Hub support for Workload Identity
jackmtpt opened this issue · 9 comments
Motivation
- Falco Sidekick is using a deprecated library (azure-event-hubs-go) to connect to Azure Event Hubs
- This doesn't seem to support Workload Identity, only the old/unsupported Pod Identity
- https://github.com/Azure/azure-sdk-for-go/blob/main/sdk/messaging/azeventhubs/README.md is apparently the new library to use which supports Workload ID.
Feature
AKS Workload Identity should be supported.
Hi,
Thanks for this issue, I didn't know, cause I'm not an Azure user. If you feel confident enough, you can propose a PR and I will review it anyway.
Thanks
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale
/remove-lifecycle stale
I'm not a Go developer so I won't be able to contribute a PR but the issue should not be marked as stale.
We are trying to run falco in AKS and would like this feature. Is there any date set to release the updates @Issif
I recently updated all deps for Azure but I didn't tested them, any help is welcome as I'm not familiar with AKS. Basically, by using the latest tagged image you should be able to test.
Will be fixed in the upcoming 2.29
just wanted to check if the fix is actually present in the 2.29 or has the fix release been postponed?
The 2.29.0 is out and contains the fix, the helm charts are also updated, you can try the new version.
I'm not sure helm chart was changed. Still see the old values using pod identity
