[
https://issues.apache.org/jira/browse/HADOOP-19660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18016274#comment-18016274
]
Kunal Sevkani commented on HADOOP-19660:
----------------------------------------
Draft PR without test to see if the structure looks okay -
[https://github.com/apache/hadoop/pull/7901]
cc: [~anujmodi]
> ABFS: Proposed Enhancement in WorkloadIdentityTokenProvider
> -----------------------------------------------------------
>
> Key: HADOOP-19660
> URL: https://issues.apache.org/jira/browse/HADOOP-19660
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/azure
> Affects Versions: 3.5.0, 3.4.1
> Reporter: Anuj Modi
> Priority: Major
>
> Externally Reported Enhancement:
> *Current Limitation*
> The current WorkloadIdentityTokenProvider implementation works well for
> file-based token scenarios, but it's tightly coupled to file system
> operations and cannot be easily extended for alternative token sources
> {*}Use Case{*}: *Kubernetes TokenRequest API*
> In modern Kubernetes environments, the recommended approach is to use the
> TokenRequest API to generate short-lived, on-demand service account tokens
> rather than relying on projected volume mounts.
> *Proposed Enhancement*
> I propose modifying WorkloadIdentityTokenProvider to accept a Supplier for
> token retrieval instead of being hardcoded to file operations:
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
