v6.3.0: Please remove gcloud namespace warning

[djfinnoy]

What happened? After upgrading to v6.3.0, Devspace seems to be utilizing the new gke-gcloud-auth-plugin under the hood.

There is an annoying feature of this auth plugin that prompts the user to confirm that they are targeting the correct namespace:

$ devspace build

warn Are you using the correct namespace?                                                                                                                                                     
warn Current namespace: 'argocd'                                                                                                                                                              
warn Last    namespace: 'default'                                                                                                                                                             

? Which namespace do you want to use?  [Use arrows to move, type to filter]                                                                                                                   
> argocd                                                                                                                                                                                      
  default 

What did you expect to happen instead? Just proceed without verifying the GKE namespace. The build step doesn't even deploy anything to GKE, so I am guessing that this is some sort of peculiarity with the gcloud auth mechanism employed by Devspace.

Hopefully, this functionality is toggleable, and can be disabled when Devspace utilizes gcloud for authentication.

How can we reproduce the bug? (as minimally and precisely as possible)

Swap namespaces with kubectl, and try building an image that will be pushed to a Google Artifact Registry.

My devspace.yaml:

version: v2beta1

...
images:
  app:
    image: europe-west1-docker.pkg.dev/my-org/artifacts/my-image  # Google Artifact Registry
    dockerfile: ./Dockerfile

pipelines:
  build: |-
    build_images --all 
...

Local Environment:

• DevSpace Version: 6.3.0
• Operating System: linux
• ARCH of the OS: AMD64 Kubernetes Cluster:
• Cloud Provider: google
• Kubernetes Version: v1.25.3

Anything else we need to know?

[FabianKramm]

@djfinnoy thanks for creating this issue! This warning comes directly from DevSpace and signals that the build was previously run in a different namespace, which shouldn't be related to gcloud. Since there a builds that require a kubernetes cluster (Kaniko etc.) Kubernetes is sometimes needed. You can disable this warning with:

devspace build ... --no-warn

[djfinnoy]

Ah, I see. My mistake. Is it possible to build --no-warn into pipelines, or will we need to include it everytime we use the CLI?

[FabianKramm]

@djfinnoy yes you can also do:

vars:
 DEVSPACE_FLAGS: '--no-warn'

which will always include this

[djfinnoy]

Excellent, thank you.