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

Implement all currently supported flavors of Azure authentication for ASO #3526

Closed
2 tasks done
Tracked by #3527 ...
nojnhuh opened this issue May 4, 2023 · 4 comments · Fixed by #3698
Closed
2 tasks done
Tracked by #3527 ...

Implement all currently supported flavors of Azure authentication for ASO #3526

nojnhuh opened this issue May 4, 2023 · 4 comments · Fixed by #3698
Assignees
Milestone

Comments

@nojnhuh
Copy link
Contributor

nojnhuh commented May 4, 2023

CAPZ supports several different mechanisms for authenticating to the Azure API as documented at https://capz.sigs.k8s.io/topics/multitenancy.html. ASO supports the same options (AFAICT) as described here: https://azure.github.io/azure-service-operator/guide/authentication/.

Whichever option a user chooses to authenticate with CAPZ, that should be passed through to be used for ASO.

Some more context is described in the ASO proposal: https://github.com/kubernetes-sigs/cluster-api-provider-azure/blob/main/docs/proposals/20230123-azure-service-operator.md#security-model

Dependencies

Preview Give feedback
  1. nojnhuh
  2. nojnhuh
@nojnhuh nojnhuh changed the title Implement all flavors of Azure authentication for ASO currently supported (https://capz.sigs.k8s.io/topics/multitenancy.html) Implement all currently supported flavors of Azure authentication for ASO May 4, 2023
@nojnhuh nojnhuh mentioned this issue May 4, 2023
@nojnhuh
Copy link
Contributor Author

nojnhuh commented Jun 14, 2023

Added a link in the description above to the relevant section from the ASO proposal.

@adriananeci
Copy link
Contributor

/assign

@nojnhuh
Copy link
Contributor Author

nojnhuh commented Jul 27, 2023

/milestone v1.11

@k8s-ci-robot
Copy link
Contributor

@nojnhuh: You must be a member of the kubernetes-sigs/cluster-api-provider-azure-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your Cluster API Provider Azure Maintainers and have them propose you as an additional delegate for this responsibility.

In response to this:

/milestone v1.11

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@nojnhuh nojnhuh added this to the v1.11 milestone Jul 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants