You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a setup with a private GKE cluster and a bastion through which we connect to the GKE cluster. In order to make this work we set the proxy-url value in the Kubeconfig.
➜ k get ns
NAME STATUS AGE
bsr Active 301d
cert-manager Active 342d
cluster-health Active 342d
default Active 343d
However the kubectl outdated command seems to throw a timeout error:
➜ k outdated
Searching for images ⠴failed to list namespaces: Get "https://172.11.0.6/api/v1/namespaces": dial tcp 172.11.0.6:443: i/o timeout
What I have tried so far:
Test on a cluster with public access (works)
Manually passing the --kubeconfig param (does not work)
Any ideas if this is related to the oudated plugin not properly handling proxies?
The text was updated successfully, but these errors were encountered:
mzwennes
changed the title
Plugin does not seem to support private GKE clusters
Plugin does not seem to support private GKE clusters through a proxy
Oct 4, 2022
We have a setup with a private GKE cluster and a bastion through which we connect to the GKE cluster. In order to make this work we set the
proxy-url
value in the Kubeconfig.The Kubeconfig looks something like this:
This works fine for default
kubectl
commands:However the
kubectl outdated
command seems to throw a timeout error:What I have tried so far:
--kubeconfig
param (does not work)Any ideas if this is related to the
oudated
plugin not properly handling proxies?The text was updated successfully, but these errors were encountered: