[BUG] az connectedk8s connect --enable-workload-identity fails
- Dominant language
- Python
- Stars
- 4.6k
- Forks
- 3.5k
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 60
Description
# Issue Transfer
This issue has been transferred from the Azure SDK for .NET repository, [#52372](https://github.com/Azure/azure-sdk-for-net/issues/52372).
### Please be aware that [@jeremy-morren](https://github.com/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_
Contributor guide
Assessment
This issue has not been assessed yet.