Azure Resource Manager Creation is stuck in kubernetes cluster environment

[sound13]

Query/Question
Azure resource manager creation or configuration is stuck in a springboot java application running inside a kubernetes cluster. The azure resource manager authenticate method is done using ClientSecretCredential and azure profile. There are no logs or exceptions thrown, what could be the reasons for the azure resource manager to not work in a kubernetes environment and what are the steps that needs to taken to move forward and make azure resource manager work

Why is this not a Bug or a feature Request?
The reason this is not a bug/feature request is because, the azure resource manager creation works fine for java application in kubernetes environment and for the same springboot application in VM environment

Setup (please complete the following information if applicable):

• Java Version : 8
• Library/Libraries: com.azure.resourcemanager: azure-resourcemanager: 2.1.0, com.azure:azure-core:1.45.1, com.azure:azure-identity:1.3.3, com.microsoft.azure:azure:1.3.0, com.azure:azure-core-http-netty:1.13.11, com.azure: azure-storage-blob:12.13.0, com.azure: azure-data-tables: 12.3.9

Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

• Query Added
• Setup information Added

[github-actions]

Thank you for your feedback. Tagging and routing to the team member best able to assist.

[weidongxu-microsoft]

@sound13

Please do not mix azure-resourcemanager with com.microsoft.azure:azure. They have very different dependencies (e.g. Jackson).

It may help if you can align the version of dependencies, the azure-resourcemanager 2.1.0 and com.azure:azure-identity 1.3.3 is ancient.
You may want to use azure-resourcemanager 2.37.0 with dependencies (azure-core etc,). from BOM https://github.com/Azure/azure-sdk-for-java/tree/main/sdk/boms/azure-sdk-bom