Fix regression caused by registry-proxy

This PR fixes #4604 by adding a new selector to concerned svc/rc only.
This also reverts `kubernetes.io/minikube-addons` to `registy` for registry-proxy
so that addon manager can deploy registry-proxy when registry addon is enabled.

deploy/addons/registry/registry-proxy.yaml.tmpl

@@ -2,15 +2,15 @@ apiVersion: extensions/v1beta1
 kind: DaemonSet
 metadata:
   labels:
-    kubernetes.io/minikube-addons: registry-proxy
+    kubernetes.io/minikube-addons: registry
     addonmanager.kubernetes.io/mode: Reconcile
   name: registry-proxy
   namespace: kube-system
 spec:
   template:
     metadata:
       labels:
-        kubernetes.io/minikube-addons: registry-proxy
+        kubernetes.io/minikube-addons: registry
         addonmanager.kubernetes.io/mode: Reconcile
     spec:
       containers:

deploy/addons/registry/registry-rc.yaml.tmpl

@@ -2,6 +2,7 @@ apiVersion: v1
 kind: ReplicationController
 metadata:
   labels:
+    actual-registry: true
     kubernetes.io/minikube-addons: registry
     addonmanager.kubernetes.io/mode: Reconcile
   name: registry
@@ -13,6 +14,7 @@ spec:
   template:
     metadata:
       labels:
+        actual-registry: true
         kubernetes.io/minikube-addons: registry
         addonmanager.kubernetes.io/mode: Reconcile
     spec:

deploy/addons/registry/registry-svc.yaml.tmpl

@@ -2,6 +2,7 @@ apiVersion: v1
 kind: Service
 metadata:
   labels:
+    actual-registry: true
     kubernetes.io/minikube-addons: registry
     addonmanager.kubernetes.io/mode: Reconcile
   name: registry
@@ -12,4 +13,5 @@ spec:
   - port: 80
     targetPort: 5000
   selector:
+    actual-registry: true
     kubernetes.io/minikube-addons: registry