The gcp-auth addon automatically and dynamically configures pods to use your credentials, allowing applications to access Google Cloud services as if they were running within Google Cloud.
The addon normally uses the Google Application Default Credentials as configured with
gcloud auth application-default login. If you already have a json credentials file you want specify, such as to use a service account, set the GOOGLE_APPLICATION_CREDENTIALS environment variable to point to that file.
The addon normally uses the default gcloud project as configured with
gcloud config set project <project name>. If you want to use a different project, set the
GOOGLE_CLOUD_PROJECT environment variable to the desired project.
The pods are configured with the
GOOGLE_APPLICATION_DEFAULTS environment variable is set, which is automatically used by GCP client libraries, and the
GOOGLE_CLOUD_PROJECT environment variable is set, as are several other historical environment variables. The addon also configures registry pull secrets to allow the cluster to access container images hosted in your project's Artifact Registry and Google Container Registry.
- Start a cluster:
😄 minikube v1.12.0 on Darwin 10.15.5 ✨ Automatically selected the docker driver. Other choices: hyperkit, virtualbox 👍 Starting control plane node minikube in cluster minikube 🔥 Creating docker container (CPUs=2, Memory=3892MB) ... 🐳 Preparing Kubernetes v1.18.3 on Docker 19.03.2 ... 🔎 Verifying Kubernetes components... 🌟 Enabled addons: default-storageclass, storage-provisioner 🏄 Done! kubectl is now configured to use "minikube"
- Enable the
minikube addons enable gcp-auth
🔎 Verifying gcp-auth addon... 📌 Your GCP credentials will now be mounted into every pod created in the minikube cluster. 📌 If you don't want credential mounted into a specific pod, add a label with the `gcp-auth-skip-secret` key to your pod configuration. 🌟 The 'gcp-auth' addon is enabled
- For credentials in an arbitrary path:
export GOOGLE_APPLICATION_CREDENTIALS=<creds-path>.json minikube addons enable gcp-auth
- Deploy your GCP app as normal:
kubectl apply -f test.yaml
Everything should work as expected. You can run
kubectl describe on your pods to see the environment variables we inject.
As explained in the output above, if you have a pod you don't want to inject with your credentials, all you need to do is add the
apiVersion: apps/v1 kind: Deployment metadata: name: pytest spec: selector: matchLabels: app: pytest replicas: 2 template: metadata: labels: app: pytest gcp-auth-skip-secret: "true" spec: containers: - name: py-test imagePullPolicy: Never image: local-pytest ports: - containerPort: 80
If you had already deployed pods to your minikube cluster before enabling the gcp-auth addon, then these pods will not have any GCP credentials. There are two ways to solve this issue.
If you use a Deployment to deploy your pods, just delete the existing pods with
kubectl delete pod <pod_name>. The deployment will then automatically recreate the pod and it will have the correct credentials.
minikube can delete and recreate your pods for you, by running
minikube addons enable gcp-auth --refresh. It does not matter if you have already enabled the addon or not.