![]() ![]() If you have been following along with this series, especially Build a Kubernetes cluster with the Raspberry Pi, you will have a Kubernetes cluster provisioned in your homelab for education and tinkering. This is very useful for enthusiasts running Kubernetes clusters in their homelabs to be able to deploy and connect to Prometheus in a single click. However, the information presented is not comprehensive–it's good for an overview, but you may still wish to utilize a visualization tool such as Grafana with a more complicated dashboard to gather more specialized information.Īlong with being able to connect to an existing Prometheus stack provisioned in the cluster, Lens can install applications on your behalf, too. This is great for getting at-a-glance information about the cluster right within the Lens UI without having to go to an external dashboard. ![]() One of Lens' incredibly helpful features is its ability to connect to a Prometheus stack installed in your cluster to gather metrics about the cluster and its nodes for both current and historical data. eBook: A guide to Kubernetes for SREs and sysadmins.eBook: Running Kubernetes on your Raspberry Pi homelab.How to explain Kubernetes in plain terms.An introduction to enterprise Kubernetes.Each will let you drill down into the information about a given object, and you can even edit the objects directly in Lens. You can also view information about config maps and secrets, networking information, storage, namespaces, and events. You can see the workloads that are running: pods and deployments, daemon sets, cron jobs, etc. ![]() Once it's connected, Lens will display a ton of information about your cluster. You can manage all namespaces and workloads once Lens has connected, and there's no need to add them all. In practice, I found it best to select the default context for any cluster. As a site-reliability engineer (SRE) working on hundreds of clusters, I had dozens and dozens of "clusters" to choose from when setting up Lens. This is particularly unhelpful compared with how OpenShift creates context information in the kubeconfig file automatically for any project (namespace) you switch to. Because cluster and authentication information about the cluster for any context is included in the kubeconfig file, Lens treats each context as a different cluster, unfortunately. Next, a drop-down box will appear containing any Kubernetes contexts from your ~/.kube/config file, or you can select a custom one. Once you launch Lens, connect it to a Kubernetes cluster by clicking the + icon in the top-left corner and selecting a kubeconfig. Then you can start Lens by typing lens on the command line. ![]() $ sudo mv Lens-3.4.0.AppImage /usr /sbin /lens $ wget https: // /lensapp /lens /releases /download /v3.4.0 /Lens-3.4.0.AppImage # Download the 3.4.0 AppImage for Lens, mark it executable and copy it to your $PATH Lens can also connect to-or install-a Prometheus stack and use it to provide metrics about the cluster, including node information and health. Out of the box, Lens can connect to Kubernetes clusters using your kubeconfig file and will display information about the cluster and the objects it contains. Lens, which bills itself as "the Kubernetes IDE," is a useful, attractive, open source user interface (UI) for working with Kubernetes clusters. Such platforms, however, come with their own management challenges that require metrics, observability, and a user-friendly interface to present their huge amount of complexity. As the scale and complexity of a containerized environment increase past a human's ability to manage, container orchestration platforms such as Kubernetes become increasingly important.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |