Right now you must use an access key/sas token for reading/writing to a storage account. It should be possible to initialize a connection with a machine identity instead.
The usecase here is that when I am running the fluentd collector on my kubernetes cluster on azure I would like the logs to be shipped to azure storage. Instead of passing in a key that could be compromised I would like to use the assigned identity of the pod (or node).
jchauncey
commented
3 years ago
Right now you must use an access key/sas token for reading/writing to a storage account. It should be possible to initialize a connection with a machine identity instead.
The usecase here is that when I am running the fluentd collector on my kubernetes cluster on azure I would like the logs to be shipped to azure storage. Instead of passing in a key that could be compromised I would like to use the assigned identity of the pod (or node).
https://github.com/fluent/fluentd-kubernetes-daemonset/blob/master/docker-image/v1.14/debian-azureblob/Gemfile