Bobcares

Access Kubernetes dashboard on EKS

by | Oct 3, 2021

Want to access the Kubernetes dashboard on EKS? We can help you.

Here, at Bobcares, we assist our customers with several EKS queries as part of our AWS Support Services.

Today, let us see how our techs perform this query.

 

Access Kubernetes dashboard on EKS

Recently, we had a customer who wanted to set up a Kubernetes Dashboard on an Amazon EKS cluster.

Moving ahead, let us see how our Support Techs perform this on Linux.

  • Set up the environment

1. Initially, we install kubectl and aws-iam-authenticator.

2. Then to configure the kubeconfig file to point to the Amazon EKS control plane, we run:

$ aws eks update-kubeconfig --name EKS_ClusterName

Here, we need to provide the necessary EKS cluster name.

3. We can verify if the worker node is running in the environment using:

$ kubectl get nodes

4. Then to verify that the Kubernetes service is running in the environment, we run:

$ kubectl get svc
  • Create a Kubernetes Dashboard

1. Firstly, we deploy the Kubernetes dashboard.

2. Then we create an eks-admin service account and cluster role binding.

3. In order to forward all requests from the Amazon EC2 instance localhost port to the Kubernetes Dashboard port, we run:

$ kubectl port-forward svc/kubernetes-dashboard -n kubernetes-dashboard 6443:44

4. After that, to access the port from the local machine with an SSH tunnel, we run:

ssh -i EC2KeyPair.pem ec2-user@IP -L 6443:127.0.0.1:6443
  • Access the Kubernetes Dashboard in a browser

1. Initially, we access the Kubernetes Dashboard in a browser, enter https://xxx.x.x.x:6443.

As the dashboard loads in the browser, we will get a prompt for input.

2. Later, to get a bearer token for authentication, we return to the command line, and run:

$ kubectl -n kube-system describe secret $(kubectl -n kube-system get secret | grep eks-admin | awk '{print $1}')

3. We then copy the token from the command line output.

4. In the browser, in the Kubernetes Dashboard pop-up window, we select, Token.

5. We paste the token from the output to the Enter token box, and then choose SIGN-IN.

Eventually, we will have access to the Kubernetes Dashboard in the browser.

[Need assistance with the procedures? We’d be glad to help]

 

Conclusion

In short, we saw how our Support Techs access the Kubernetes dashboard on EKS.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF