From d9ac86498ae434924158c84f449c988bc3bf6fee Mon Sep 17 00:00:00 2001 From: Steven Powell Date: Wed, 19 Oct 2022 15:49:46 -0700 Subject: [PATCH] add documentation about adding a new namespace --- site/content/en/docs/handbook/addons/gcp-auth.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/site/content/en/docs/handbook/addons/gcp-auth.md b/site/content/en/docs/handbook/addons/gcp-auth.md index 21b6d2fe62af..82ba58a99a85 100644 --- a/site/content/en/docs/handbook/addons/gcp-auth.md +++ b/site/content/en/docs/handbook/addons/gcp-auth.md @@ -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 `. 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`.