![Lead Image © Noel Powell, Fotolia.com Lead Image © Noel Powell, Fotolia.com](/var/ezflow_site/storage/images/archive/2020/59/dig-deep-into-kubernetes-with-statusbay/noel_powell_fotolia-telescope.png/177333-1-eng-US/Noel_Powell_Fotolia-Telescope.png1_medium.png)
Lead Image © Noel Powell, Fotolia.com
Dig Deep into Kubernetes with StatusBay
Night Vision
After the explosive adoption of containers, resulting in Kubernetes stoically taking the orchestrator reins, a number of useful tools were created in order to assist the orchestrator run containers efficiently. Every possible advantage is welcome when you're trying to keep a critical service online, and StatusBay is "an open source tool that provides the missing visibility into the K8s deployment process" [1].
In this article I look at the clever StatusBay, which is available on GitHub courtesy of an international company called SimilarWeb [2]. According to a posting on Reddit, StatusBay was recently released as open source, having been a tool "that was used internally for a long time now" [3]. To demonstrate StatusBay in action, the tech stack will include a miniscule Kubernetes distribution, K3s [4] (offered by Rancher [5]), to build a Kubernetes cluster, and the Kubernetes package manager, Helm.
A great deal of information about where to begin with K3s can be found in one of my previous articles, "Kubernetes k3s Lightweight Distro" [6], which discusses using the magically tiny K3s within Internet of Things (IoT) applications.
The name of K3s came from Kubernetes' often abbreviated form K8s; according to the docs on the Rancher website, "something half as big as Kubernetes would be a 5-letter word stylized as K3s. There is no long form of K3s and no official pronunciation" [7]. As a certified distribution sitting at less than 50MB (and using less than half the RAM of a standard cluster) the binary that runs K3s is a sight to behold
...Buy this article as PDF
(incl. VAT)