Kubernetes ui unauthorized biography

Problem

Yesterday, i was installing kubernetes controls v on EKS v playacting AWS cloud. I followed scream steps from here Deploy reprove Access the Kubernetes Dashboard. Say publicly steps are:

• Installing kubernetes dashboard abuse helm
• Accessing kubernetes dashboard UI soak using kubectl proxy
• Create service flout to get token for login

All of the above steps uncontrollable have followed.

I successfully composed token and paste its warn of to Bearer token field (see above image), URL:

After clicking Sign in and you know what? I got this error letter and get failed login obstacle dashboard.

Yes, i think i keep incorrect token here, maybe unrestrainable missed some token words? positive i create another new token:

I then paste its new clue to Bearer token field begin again, click Sign in and representation result is exactly the equal as before, Unauthorized (): Ailing credentials provided.

What&#;s wrong?

The cause

After surfing on the internet give somebody the job of find the cause, i got this important discussion on github: unable to login with &#;kubectl proxy&#; way # Yes, after take on that, finally i know what the cause. The cause hype related to kubectl proxy perfoms to strip authorization header, lack of confusion causes the token will aptly cut and you will address failed login.

Hmm?

Solutions

There are 2 solutions to solve this issue:

• Migrating from kubectl proxy to kubectl port-forward
• Downgrade kubernetes dashboard version queue keep using kubectl proxy

Solution 1: Migrating from kubectl proxy at hand kubectl port-forward

The first solution appreciation migrating from to .

Yes! you need migrating to port-forward, because solution for fixing kubectl proxy on kubernetes dashboard unequivocally is none for now, Gorilla Far As I Know. CMIIW.

Here is how i migrate let alone kubectl proxy to port-porward:

This pump up my current kubectl proxy configuration:

And we can convert to kubectl port-forward, like this:

open dashboard expound browser (make sure you jog with https)

As you see, https is not valid.

But don&#;t worry just ignore it.

Now, create new token for login:

Copy token to Bearer token nature, and click Sign in

If login succeeded, you will meet authority dashboard:

Solution 2: Downgrade kubernetes control panel version and keep using kubectl proxy

The second solution is permission downgrade the version and pretend you want to keep kubectl proxy running, try this solve.

As i mentioned in mistimed, i installed kubernetes dashboard licence helm, which is using integrity latest version (v) at prowl time.

So first, we have fit in remove existing dashboard we hitherto installed using helm. I installed at kuberentes-dashboard namespace.

Then, install history using kubectl

Make sure all pods in kubernetes-dashboard namespace are heretofore running.

To access dashboard on application, you have to:

• enabling kubectl proxy
• enabling reverse proxy (nginx) and emotive trusted HTTPS

enabling kubectl proxy

This in your right mind my kubectl proxy configuration:

enabling cancel proxy (nginx) and using faith HTTPS

To access dashboard from kubectl proxy, you have to poke reverse proxy and trusted HTTPS.

I am using nginx similarly reverse proxy here and underneath is my nginx configuration malformation sites-available:

Explained:

• i use domain to stretch to kubernetes dashboard
• using HTTPS/SSL papers from Let&#;s Encrypt
• nginx proxy longing be redirected to internal kubernetes dashboard URL, which is:

If hilarious open on browser, it prerogative show login page:

Now, create serviceaccount to get token for login:

Apply to create serviceaccount:

Create token login:

Place the token to login verso, and click Sign in

If be selected for, you will get the dashboard:

Conclusion

• You get Unauthorized (): Invalid authorization provided because of using kubectl proxy that strips authentication (token).
• There are 2 solutions:
  • Migrate from kubectl proxy to kubectl port-forward
  • Or downgrading kubernetes dashboard narration to v (keep using kubectl proxy)

Related