K
Q

Kubernetes AWS Dashboard Questions

8/12/2017

I have a working Kubernetes gossip-based cluster deployed on AWS using Kops. I also have the dashboard running on localhost:8001 on my local machine. If I understand correctly this URL https://kubernetes.io/docs/admin/authentication/ gives the different ways to expose the dashboard properly among other things.

  1. Whats the easiest and simplest steps to expose the cluster's dashboard across internet?
  2. What are the disadvantages of using the gossip based cluster?
  3. Is it all right to stop my EC2 instances when I am not using the cluster? Are there any reconfiguration steps needed when the EC2 instances are restarted? Is there any sequence in which the EC2 instances must be restarted? [I realised that 3 is a bad question and the autoscaling group will cause another ec2 instance to start for each stopped ec2 instance (the kubernetes people and kops people are too good and the jokes on me). That said how can I stop/start the kubernetes cluster when I am not using it]/when I need it
-- Raster R
amazon-web-services
dashboard
kops
kubernetes

Similar Questions

Possible OOM in GCP container – how to debug?
Snapshotting on google cloud/Kubernetes when using storageClass persistent volumes
Kubernetes: Expose only single pod of StatefulSet
Can't connect to mysql pod in Kubernetes when using Secrets for password (Access denied)

1 Answer

9/3/2017

Just making sure some one else finds this useful. If you are trying to save costs when not using the kops kubernettes cluster on aws there are these options. 1. Tear it down completely.(you can rebuild it later) OR 2. In the 2 autoscale groups edit the min,desired,max to 0. This will bring down the cluster(you can later revert these values and the cluster will be back on its own)

Thanks. R

-- Raster R
Source: StackOverflow