Asking for help? Comment out what you need so we can get more information to help you!
Cluster information:
Kubernetes version: v1.29.3+k3s1
Cloud being used: bare-metal
Installation method: Helm chart via Lens
Host OS: Ubuntu 22.04 (on VM with MacOS 14.3 host)
CNI and version: flannel (unsure which version. default for this version of k3s)
CRI and version: v1.7.11-k3s2
I’ve followed the instructions to create a sample user with k8s dashboard access, including creating the long-running bearer token. I’m running the port-forward to the kong-proxy service as specified. However, I can’t access the dashboard with token sign-in. I’ve tried with localhost, 127.0.0.1, 0.0.0.0. This also occurred with k0s and with short-lived bearer token as well
The token looks like this: eyJhb...V8Ew
There is only one network request/response that looks suspicious, although it basically looks like the token is unable to be authenticated:
GET /api/v1/me HTTP/2
→ {"ErrStatus":{"metadata":{},"status":"Failure","message":"MSG_LOGIN_UNAUTHORIZED_ERROR","reason":"Unauthorized","code":401}}
I’m wondering what is wrong here to allow the sign-in button to work?