Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for workload identity addon on AKS #18666

Closed
1 task done
jkroepke opened this issue Oct 8, 2022 · 2 comments
Closed
1 task done

Support for workload identity addon on AKS #18666

jkroepke opened this issue Oct 8, 2022 · 2 comments

Comments

@jkroepke
Copy link
Contributor

jkroepke commented Oct 8, 2022

Is there an existing issue for this?

  • I have searched the existing issues

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Following https://learn.microsoft.com/en-us/azure/aks/workload-identity-deploy-cluster, the workload identity addon in addition to the OIDC issuer is required on AKS to use it.

Quote from az cli

    --enable-workload-identity                    : Enable workload identity addon.  Allowed values:
                                                    false, true.

Currently, its not possible to enable this through terraform.

New or Affected Resource(s)/Data Source(s)

azurerm_kubernetes_cluster

Potential Terraform Configuration

resource "azurerm_kubernetes_cluster" "jok" {
  workload_identity_enabled = true
}

References

https://learn.microsoft.com/en-us/azure/aks/workload-identity-deploy-cluster

@stephybun
Copy link
Member

Thanks for raising this issue @jkroepke. AFAIK workload identity is synonymous with Pod Identity v2 which is being tracked in #9885. Please subscribe to #9885 for updates.

Thanks!

@github-actions
Copy link

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 13, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants