registry-creds addon stopped working in Minikube 0.26.0

476 views
Skip to first unread message

jim.b...@healthengine.com.au

unread,
Apr 10, 2018, 11:21:43 PM4/10/18
to Kubernetes user discussion and Q&A
Hi.

I've been playing around with Minikube, and part of that was using the
registry-creds addon to allow access to pull Docker images from AWS ECR.
With Minikube 0.25.2 this was working fine, but is broken using 0.26.0.

I deleted the cluster and set it up again using Minikube 0.26.0.
I have configured the registry-creds addon, and it created the
registry-creds-dpr, registry-creds-ecr, and registry-creds-gcr secrets in the
kube-system namespace.
However, the addon is not creating the awsecr-cred and dpr-secret secrets in the
other name spaces.
I've checked the content of the registry-creds-* secrets and they look valid.

I've ssh'ed to the Minikube VM and looked at the logs for the container called
k8s.gcr.io/kube-addon-manager.
In the logs are messages like so:

The ReplicationController "registry-creds" is invalid: spec.template.metadata.labels: Invalid value: map[string]string{"addonmanager.kubernetes.io/mode":"Reconcile", "name":"registry-creds", "version":"v1.8"}: `selector` does not match template `labels`

I don't know if it used to do that in the older version of Minikube or not, but
I have a feeling this is cause of the issue.

Regards,
Jim Barber

jim.b...@healthengine.com.au

unread,
Apr 11, 2018, 12:08:22 AM4/11/18
to Kubernetes user discussion and Q&A
I have found there is a problem with the
/etc/kubernetes/addons/registry-creds-rc.yaml manifest.

It starts out like so:

apiVersion: v1
kind: ReplicationController
metadata:
name: registry-creds
namespace: kube-system
labels:
version: v1.9
addonmanager.kubernetes.io/mode: Reconcile
kubernetes.io/minikube-addons: registry-creds
spec:
replicas: 1
selector:
name: registry-creds
version: v1.9
addonmanager.kubernetes.io/mode: Reconcile
template:
metadata:
labels:
name: registry-creds
version: v1.8
addonmanager.kubernetes.io/mode: Reconcile

The v1.8 is wrong, and if I change it to v1.9 and kill the kube-addon-manager
container so that it restarts, then everything starts working.

Rohit Agarwal

unread,
Apr 11, 2018, 1:55:33 AM4/11/18
to kubernet...@googlegroups.com

--
You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-use...@googlegroups.com.
To post to this group, send email to kubernet...@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages