Kubernetes dashboard in aws EC2 instance?

how to access kubernetes dashboard remotely
kubernetes dashboard kustomize
kubernetes dashboard metrics-server
kubernetes dashboard-token
kubernetes dashboard alternative
kubernetes dashboard eks
kubernetes-dashboard dockerfile
eks dashboard without proxy

I have started 2 ubuntu 16 EC2 instance(one for master and other for worker). Everything working OK. I need to setup dashboard to view on my machine. I have copied admin.ctl and executed the script in my machine's terminal

 kubectl --kubeconfig ./admin.conf proxy --address='0.0.0.0' --port=8002 --accept-hosts='.*' 

Everything is fine. But in browser when I use below link

http://localhost:8002/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/

I am getting Error: 'dial tcp 192.168.1.23:8443: i/o timeout' Trying to reach: 'https://192.168.1.23:8443/'

I have enabled all traffics in security policy for aws. What am I missing? Please point me a solution

If you only want to reach the dashboard then it is pretty easy, get the IP address of your EC2 instance and the Port on which it is serving dashboard (kubectl get services --all-namespaces) and then reach it using: First:

kubectl proxy --address 0.0.0.0 --accept-hosts '.*'

And in your browswer:

http://<IP>:<PORT>/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/#!/login

Note that this is a possible security vulnerability as you are accepting all traffic (AWS firewall rules) and also all connections for your kubectl proxy (--address 0.0.0.0 --accept-hosts '.*') so please narrow it down or use different approach. If you have more questions feel free to ask.

Set Up a Kubernetes Dashboard on an Amazon EKS Cluster, If you only want to reach the dashboard then it is pretty easy, get the IP address of your EC2 instance and the Port on which it is serving  3 Answers3. active oldest votes. 2. If you only want to reach the dashboard then it is pretty easy, get the IP address of your EC2 instance and the Port on which it is serving dashboard ( kubectl get services --all-namespaces) and then reach it using: First: kubectl proxy --address 0.0.0.0 --accept-hosts '.*'. And in your browswer:

Have you tried putting http:// in front of localhost?

I don't have enough rep to comment, else I would.

Kubernetes dashboard in aws EC2 instance?, Steps to reproduce. Installed Kubernetes on 1 Master and 3 Slave EC2 instance using kubeadm. Used Canal add-on. Installed certificates using  To forward all requests from your Amazon EC2 instance localhost port to the Kubernetes dashboard port, run the following command: $ kubectl port-forward svc/kubernetes-dashboard -n kube-system 6443:443

For bypassing dashboard with token. You have to execute the below code

cat <<EOF | kubectl create -f -
apiVersion: rbac.authorization.k8s.io/v1beta1
kind: ClusterRoleBinding
metadata:
  name: kubernetes-dashboard
  labels:
    k8s-app: kubernetes-dashboard
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: cluster-admin
subjects:
- kind: ServiceAccount
  name: kubernetes-dashboard
  namespace: kube-system
EOF

After this you can skip without providing token. But this will cause security issues.

Installing a Kubernetes Dashboard on AWS, not able to access kubernetes dashboard for cluster in an existing vpc in aws-ec2 instance. #2994. Closed. ishanupadhyay opened this issue on  CoreOS Tectonic includes the open-source Tectonic Installer that creates Kubernetes clusters with Container Linux nodes on AWS. CoreOS originated and the Kubernetes Incubator maintains a CLI tool, kube-aws , that creates and manages Kubernetes clusters with Container Linux nodes, using AWS tools: EC2, CloudFormation and Autoscaling.

Way to access Dashboard running in AWS master node from my , The official Kubernetes dashboard is not deployed by default, but there are instructions in the We can deploy the dashboard with the following command: This is a guide for setting up a Kubernetes cluster over AWS EC2 instances from scratch. Let’s start with the prerequisites first. Prerequisites: You need to have created at least one AWS EC2 instance for acting as Master node and at least one AWS EC2 instance to act as a worker node.

not able to access kubernetes dashboard for cluster in an existing , Why: While the venerable Kubernetes Dashboard is still a popular to deliver AWS IAM credentials to single-tenant EC2 instances uses the  Setup Kubernetes Cluster on AWS EC2: You can either setup AWSCLI on your local machine or launch a new EC2 instance with IAM role that has administrator access. In thistutorial I will be using AWS EC2 instances for setting up Kubernetes cluster. Create a new role with Administrator Access.

Deploy the Official Kubernetes Dashboard :: Amazon EKS Workshop, The Kubernetes Dashboard is a web-based interface you can use to manage your EKS requires that all worker node EC2 instances have a tag with the key  How to Create a Kubernetes Cluster on AWS in Few Minutes. The node size or rather the EC2 instance type would need to be decided you may need to deploy the Kubernetes dashboard to access

Comments
  • I am getting this Error: 'tls: oversized record received with length 20527' Trying to reach:'10.2##.1.##:9090' when giving xxxx:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/ –
  • I see two possibilities here, either you use outdated Kubernetes dashboard - in that case please delete it and install from official GitHub page. Or try to change https to http - but I recommend deleting old dashboard and installing the proper one (you can do it for example by kubectl delete -f *enter old yaml used for dashboard deployment*. If this will not fix the problem please provide results of kubectl get services --all-namespaces
  • I got inside dashboard, but it is showing some error inside the page in yellow tab. --> configmaps is forbidden: User "system:serviceaccount:kube-system:kubernetes-dashboard" cannot list resource "configmaps" in API group "" in the namespace "default" + Show 12 more
  • did you reach the site where you should have put the authorization token? Also it could be a problem with RBAC. You could try creating a user: github.com/kubernetes/dashboard/wiki/Creating-sample-user
  • Thanks for the support, I added ClusterRoleBinding as my friend suggested. So i can skip token but it will impose security risks. Anyway I can test with this.
  • In browser, by default it will take http