-
Notifications
You must be signed in to change notification settings - Fork 55
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
Wire up kubelet credential provider properly in capz templates #446
Comments
/assign @ritikaguptams |
@jsturtevant: GitHub didn't allow me to assign the following users: ritikaguptams. Note that only kubernetes-sigs members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. In response to this:
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-sigs/prow repository. |
Signed-off-by: James Sturtevant <jsturtevant@gmail.com>
update skip until #446 is resolved
/assign @ritikaguptams |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
This will not be in the community sub, we will move this to a private registry in the private sub and use kubelet credential provider to access it. we need to wire this in to our templates but the credential binaries are already there kubernetes-sigs/cluster-api-provider-azure#4679 (comment)
Originally posted by @jsturtevant in #444 (comment)
The text was updated successfully, but these errors were encountered: