Skip to content

Commit

Permalink
Merge pull request #15175 from spowelljr/gcpAuth
Browse files Browse the repository at this point in the history
site: Add documentation about adding a new namespace with GCP-Auth
  • Loading branch information
spowelljr authored Oct 20, 2022
2 parents f4cd0fb + d9ac864 commit a4e5880
Showing 1 changed file with 4 additions and 0 deletions.
4 changes: 4 additions & 0 deletions site/content/en/docs/handbook/addons/gcp-auth.md
Original file line number Diff line number Diff line change
Expand Up @@ -98,3 +98,7 @@ If you had already deployed pods to your minikube cluster before enabling the gc
1. 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.

2. 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.

## Adding new namespaces

If you have created a new namespace after enabling the gcp-auth addon, then the namespace will be missing the image pull secret. To resolve this issue run `minikube addons enable gcp-auth --refresh`.

0 comments on commit a4e5880

Please sign in to comment.