‫Another important part of any of these orchestrators
‫is to have a web GUI.
‫It's kind of a standard thing now.
‫If you're going to run a system, a large,
‫multi-server system, you'd need some sort of GUI
‫interface to at least give you some visualizations.
‫Some things more than just a standard command line that you
‫can put up on a pretty, you know, wall
‫LCD screen that everybody gets to look at.
‫Something like that, right. Of course, you're going to have
‫people on your team that are going to want a GUI.
‫They're not going to want to be experts in the command line
‫because they're really just operating.
‫They're just looking at things and maybe uploading some
‫YAML, or changing some pods or something.
‫The nice thing is with Kubernetes is you do get one.
‫It's not out-of-the-box, but it is an official project
‫called the Kubernetes Dashboard.
‫There are third-party ones, but really,
‫I think that everyone kind of is used to the standard
‫default one, then maybe consider a third-party one.
‫Of course, if you do a distribution like Docker Enterprise,
‫or Rancher, or something like that, they're going to have
‫their out-of-the-box as well.
‫That would really replace the default
‫Kubernetes Dashboard that you might install.
‫The Dashboard is actually really easy to use and it's easy
‫to install. Do realize, though, that if you're in the Cloud
‫and you're using what I would recommend in the Cloud is
‫their Kubernetes, where you're just deploying on
‫Azure, or Amazon, or DigitalOcean.
‫You're just deploying their hosted Kubernetes where they
‫have the managers, and you're just getting a bunch of
‫worker nodes to put your stuff on.
‫They don't really typically give you this GUI by default.
‫So, you will want to deploy it to
‫at least see what's going on your cluster.
‫But, they don't have a lot
‫of tools for you. They're really just automating the
‫management of the service.
‫That might change, but for now at least, a lot of these,
‫you will want to deploy this Dashboard for yourself.
‫The last thing I want to say here is safety first on
‫this one. There have actually been documented cases,
‫including a couple of very big tech companies in the US,
‫that have been hacked mostly through this dashboard.
‫I think a lot these problems have been solved in the recent
‫releases, but a lot of these things will come
‫out-of-the-box with no great authentication or no
‫authentication at all.
‫You should always assume that if you're putting something
‫on the Internet, it's going to be attempted to be hacked,
‫right. Someone's going to try to do it, especially if it's
‫on a common port.
‫For any dashboard you use, or
‫really any of these ports, but mostly these administrative
‫dashboards, because they're more likely to be
‫vulnerable to something whether it's cross-site scripting,
‫or some web framework vulnerability, that
‫you put them on random ports, or you protect their
‫IP through IP limiting to maybe just your office,
‫or maybe you require a VPN of some sort.
‫For my small projects, personally, I just tend to use
‫random high ports, or I put some
‫sort of proxy in front of it that requires authentication.
‫So, you can't even really talk to the Kubernetes Dashboard
‫until you first authenticate.
‫Kubernetes Dashboard itself does have authenticating
‫options, and it does come out-of-the-box with some stuff.
‫But just word of advice.
‫Don't be one of those people that ends up in the headlines
‫because the Kubernetes got hacked at your office and
‫bitcoin miners started mining data on your
‫systems because it had access.
‫If you just kind of Google around, you'll find some cases
‫where that's really happened to major companies.