[BUG] az connectedk8s connect --enable-workload-identity fails

[jsquire]

Issue Transfer

This issue has been transferred from the Azure SDK for .NET repository, #52372.

Please be aware that @jeremy-morren is the author of the original issue and include them for any questions or replies.

Details

Library name and version

Azure CLI 2.76.0

Describe the bug

Running command az connectedk8s connect --enable-workload-identity succeeds, but leaves the extension in state Creating. Running az connectedk8s connect then az connectedk8s update --enable-workload-identity works.

(Note: All commands were also run with --enable-oidc-issuer)

Expected behavior

az connectedk8s connect --enable-workload-identity should successfully enable workload identity.

Actual behavior

az connectedk8s connect --enable-workload-identity succeeds (there is an error printed), and leaves workload identity in state Creating

Reproduction Steps

Run command az connectedk8s connect --enable-workload-identity and view workload identity extension status.

Environment

No response

[yonzhan]

Thank you for opening this issue, we will look into it.

[jeremy-morren]

Sorry, added the issue in the wrong repository.

[microsoft-github-policy-service]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @akashkeshari.