This message was deleted.
# general
a
This message was deleted.
c
Trying to access what? The Kubernetes apiserver? A service deployed to the cluster? How are you accessing it? 403 suggests that you are not authenticating properly, what are you using for auth? Why are you using postman?
b
Trying to access The Kubernetes apiserver to configure it from an external system
creating deployments and checkng pod statuses etc.
c
Ok so how are you authenticating? The default admin kubeconfig uses client cert auth.
b
I found some instructions here "https://rancher.com/docs/k3s/latest/en/installation/kube-dashboard/" to create a service account. I generated a token to authenticate myself. It was working yesterday as follows: "curl -k -XGET -H "Accept: application/json" -H "Authorization: Bearer $TOKEN" https://10.10.10.185:6443/api/v1/pods -k". Today, it doesn't anymore. Is this the recommended method?
c
Possibly a dumb question, but do you still have $TOKEN set in your shell?
b
I typed it that way for the channel. I use the real token value in my curl