KeyVault getSecret() hangs when run inside kubernetes

Describe the bug

In versions of Azure-core 1.2x, and 1.3x there seems to be a bug that afflicts the azure-security-keyvault-secrets package while running in Kubernetes. The bug is that while running a java spring application in a Kubernetespod, the getSecret call just hangs and the program locks up and never recovers. I noticed the pod is getting CPU throttled but there is very little diagnostic information available to try and troubleshoot. There is another github thread found below which provide more detail and some suggestions (None of which work) - See additional context for link to thread. The solution for me ended up being downgrading azure-core to 1.1x

Can you please look at correcting this? I am forced to run old version of the Azure-core, Cosmos, and keyvault libraries which are missing a lot of great enhancements.

Exception or Stack Trace No stack trace, the application just hangs.

To Reproduce Run a java application in k8s with java 8, spring, and Azure-core 1.2x and 1.3x, then try to call secretClient.getSecret(secret).getValue()

Code Snippet LOGGER.info(“Initializing Keyvault Client…”);

secretClient = new SecretClientBuilder()
		.vaultUrl(properties.getKeyVaultUri())
		.addPolicy(new TimeoutPolicy(Duration.ofSeconds(100)))
		.credential(
				new ClientSecretCredentialBuilder()
						.clientSecret(properties.getKeyVaultClientSecret())
						.clientId(properties.getKeyVaultClientId())
						.tenantId(properties.getKeyVaultTenantid())
						.build())
		.clientOptions(httpClientOptions)
		.buildClient();

secret = secretClient.getSecret(secret).getValue();

Expected behavior We can retrieve the key without the code freezing.

Setup (please complete the following information):

• OS: Linux
• IDE: N/A
• Library/Libraries: Azure-core 1.2x or 1.3x
• Java version: 8
• App Server/Environment: Kubernetes
• Frameworks: Spring boot

Additional context Heres another thread with more context, the issue was created for the keyvault client but I think that is not where the issue exists given that keyvault version changes didnt fix the issue but Azure-core package version downgrade did. https://github.com/Azure/azure-sdk-for-java/issues/28364

[joshfree]

Hi @bennydean thank you for reaching out to us via this GitHub issue. @vcolin7 from the KeyVault SDK team will follow up with you shortly.

[vcolin7]

@bennydean, I think @anuchandy and I have a lead to where this might be happening in the stack and I will be looking into this next week.