-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
minikube addons enable registry-creds Failed #10022
Comments
Hey @steephengeorge looks like this is a known issue with minikube version 1.15.x This should have been fixed by #9733 Could you try upgrading to our latest release, v1.16.0, to see if that resolves the issue? Thank you! |
@priyawadhwa Thank you for the info. Windows choco didn't yet support V1.16.0. I will hack it and let you know |
@steephengeorge sounds good, please let us know if the newest version works for you! |
@steephengeorge Any update? |
It worked as expected. You can close this ticket.
…On Thu, Feb 11, 2021 at 1:16 AM Steven Powell ***@***.***> wrote:
@steephengeorge <https://github.com/steephengeorge> Any update?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#10022 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAC7F5ECRCGA45ACDWM6MS3S6LPAFANCNFSM4VFFSGDQ>
.
|
It is working as expected with version v1.17.1 |
I am trying to set up Minikube in my local Windows machine against AWS ECR by following the instructions from here.
I successfully ran
minikube addons configure registry-creds
But it failed in following step
minikube addons enable registry-creds
minikube version: v1.15.1 with VirtualBox
commit: 23f40a0
Windows 10
I compared the latest version of registry-creds-rc.yaml with my local version, both are same.
The text was updated successfully, but these errors were encountered: