k9s icon indicating copy to clipboard operation
k9s copied to clipboard

Published 20 hours ago • verified publisher icon derailed

Watcher failed for apps/v1/deployments

Open bpoetzschke opened this issue 3 years ago • 7 comments

I recently updated to v0.25.18 and I started to receive the following error when trying to change to deployments.

ERR component init failed for "Deployment" error="`list access denied for user on \"\":apps/v1/deployments"
ERR Watcher failed for apps/v1/deployments -- [list watch] access denied on resource "":"apps/v1/deployments"

I also got a similar message when trying to access pods or other resources. Furthermore, I verified my general k8s access with kubectl and it worked.

I downgraded now to v0.25.8 and do not experience the issue anymore.

mac: 12.1 (21C52) go version go1.17.5 darwin/amd64

bpoetzschke avatar Jan 05 '22 16:01 bpoetzschke

This seems to be kubernetes version related, k9s v0.25.18 works still fine on a v1.19.14 cluster but fails with the watcher error on a v1.20.11 cluster

I went backwards version by version: v0.25.13 is the last version that works on the v1.20 cluster.

adrobisch avatar Jan 14 '22 13:01 adrobisch

Hi,

Same issue for v1.21.1 K8s cluster.

mug-3-n avatar Feb 25 '22 10:02 mug-3-n

I don't think anymore that this is cluster related, deleting .config/k9s/config.yml can fix this. This was tested with a gcloud access config on GKE.

adrobisch avatar Feb 28 '22 16:02 adrobisch

Hi,

I confirm the observation of @adrobisch. By changing the environment variable KUBECONFIG, the problem occurs. Then deleting the .config/k9s/config.yml file temporarily fixes the problem until the next KUBECONFIG change.

mug-3-n avatar Feb 28 '22 16:02 mug-3-n

Same issue with k8s v1.20.11

davic80 avatar Jun 17 '22 07:06 davic80

In my case, k9s generate .config/k9s/config.yml and add default to the active namespace, which however my config does not have the permission to access.

just fix the .config/k9s/config.yml and everything just fine.

tataue avatar Jul 07 '22 15:07 tataue

I found that you can launch k9s with a specific context that you have created with kubectl, and it should not only work, but change your .config/k9s/config.yml active namespace

k9s --context $context

dmlond avatar Jul 29 '22 20:07 dmlond

Deleting config didn't help in my case. However setting namespace explicitly in my context (as suggested in a separate issue) helped.

kubectl config set-context --current --namespace=default

obok avatar Apr 03 '23 17:04 obok

Hi @bpoetzschke! Can I close this issue? You can create a new one with more details if you still facing this (or another) problem!

slimus avatar Apr 03 '23 19:04 slimus

@slimus it seems the issue no longer persists for me with an upgraded k8s version and the latest version of the k9s. So I will close it.

bpoetzschke avatar Apr 03 '23 19:04 bpoetzschke