adding the label to gvisor and ingress, and documentation

deploy/addons/gvisor/gvisor-pod.yaml.tmpl

@@ -20,6 +20,7 @@ metadata:
   labels:
     addonmanager.kubernetes.io/mode: Reconcile
     kubernetes.io/minikube-addons: gvisor
+    gcp-auth-skip-secret: "true"
 spec:
   hostPID: true
   containers:

deploy/addons/ingress-dns/ingress-dns-pod.yaml

@@ -34,6 +34,7 @@ metadata:
     kubernetes.io/bootstrapping: rbac-defaults
     app.kubernetes.io/part-of: kube-system
     addonmanager.kubernetes.io/mode: Reconcile
+    gcp-auth-skip-secret: "true"
 rules:
   - apiGroups:
       - ""

deploy/addons/ingress/ingress-dp.yaml.tmpl

@@ -44,6 +44,7 @@ spec:
         app.kubernetes.io/instance: ingress-nginx
         app.kubernetes.io/component: controller
         addonmanager.kubernetes.io/mode: Reconcile
+        gcp-auth-skip-secret: "true"
     spec:
       serviceAccountName: ingress-nginx
       containers:

site/content/en/docs/contrib/addons.en.md

@@ -23,6 +23,10 @@ Add your manifest YAML's to the directory you have created:
 
 `cp *.yaml deploy/addons/<addon name>`
 
+Note: If the addon never needs authentication to GCP, then consider adding the following label to the pod's yaml:
+
+`gcp-auth-skip-secret: "true"`
+
 To make the addon appear in `minikube addons list`, add it to `pkg/addons/config.go`. Here is the entry used by the `registry` addon, which will work for any addon which does not require custom code:
 
 ```go