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

Extend UserAssignedIdentity operatorSpec with secrets #3936

Closed
mehighlow opened this issue Apr 12, 2024 · 0 comments · Fixed by #3937
Closed

Extend UserAssignedIdentity operatorSpec with secrets #3936

mehighlow opened this issue Apr 12, 2024 · 0 comments · Fixed by #3937

Comments

@mehighlow
Copy link
Contributor

Describe the current behavior
UserAssignedIdentity can expose clientId, tenantId, and principalId in the form of a ConfigMap.

Describe the improvement
UserAssignedIdentity can expose clientId, tenantId, and principalId in the form of Secrets alongside ConfigMap.

Additional context
Some types of installations may require the secretKeyRef method for delivering Managed Identity credentials to the pod, either by design or for security reasons. Azure Service Operator (ASO) already supports exposing ConfigMaps and Secrets for a variety of resources. This functionality would extend to UserAssignedIdentity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

Successfully merging a pull request may close this issue.

2 participants