upmc-enterprises / registry-creds

Allow for AWS ECR, Google Registry, & Azure Container Registry credentials to be refreshed inside your Kubernetes cluster via ImagePullSecrets
Other
344 stars 124 forks source link

Addons registry-creds cannot be configured for AWS Elastic Container Registry #78

Open peteryhwong opened 5 years ago

peteryhwong commented 5 years ago

I have also reported this at https://github.com/kubernetes/minikube/issues/5753. Not sure if this is the right place to report.

The exact command to reproduce the issue:

minikube start
minikube addons configure registry-creds

The full output of the command that failed:

😄 minikube v1.5.0 on Darwin 10.15 ✨ Automatically selected the 'hyperkit' driver (alternates: [virtualbox]) 🔥 Creating hyperkit VM (CPUs=2, Memory=2000MB, Disk=20000MB) ... 🐳 Preparing Kubernetes v1.16.2 on Docker 18.09.9 ... 🚜 Pulling images ... 🚀 Launching Kubernetes ... ⌛ Waiting for: apiserver proxy etcd scheduler controller dns 🏄 Done! kubectl is now configured to use "minikube"

Do you want to enable AWS Elastic Container Registry? [y/n]: y -- Enter AWS Access Key ID: my-access-key -- Enter AWS Secret Access Key: my-secret-key -- (Optional) Enter AWS Session Token: -- Enter AWS Region: ap-southeast-1 -- Enter 12 digit AWS Account ID (Comma separated list): my-account-id -- (Optional) Enter ARN of AWS role to assume:

Do you want to enable Google Container Registry? [y/n]: n

Do you want to enable Docker Registry? [y/n]: n ❌ ERROR creating registry-creds-ecr secret: Temporary Error: secrets "registry-creds-ecr" not found ❌ ERROR creating registry-creds-gcr secret: Temporary Error: secrets "registry-creds-gcr" not found ⚠️ ERROR creating registry-creds-dpr secret ✅ registry-creds was successfully configured

The output of the minikube logs command:

No logs output due to the command minikube addons configure registry-creds

The operating system version:

macOS Catalina 10.15 minikube version: v1.5.0 commit: d1151d93385a70c5a03775e166e94067791fe2d9

bmwant commented 4 years ago

Try updating your minikube and then

minikube delete --all --purge