Felix Matouschek

Looks like a deeper rooted issue with virtctl and authentication on GKE clusters when accessing the GKE cluster's API. The issue is not with the VM itself. I need a...

In separate shell run: ``` kubectl proxy [...] Starting to serve on 127.0.0.1:8001 ``` Create file `kubeconfigproxy` with following contents: ``` apiVersion: v1 kind: Config clusters: - cluster: server: http://localhost:8001...

As I said I need a GKE cluster to examine this further, I will see what I can do next week.

/reopen /remove-lifecycle rotten

Possible fix in https://github.com/kubevirt/kubevirt/pull/12460

@samforger Can you try this again with the latest main of KubeVirt?

There are nightly builds you can try with: https://kubevirt.io/user-guide/cluster_admin/installation/#installing-the-daily-developer-builds

/cc @alicefr

/sig code-quality

@fabiand Good idea, I will create a proposal PR for `docs/coding-conventions.md`. I expect the conventions we agree upon will be discussed in the PR.