2 One single pane of glass

 

Melika Golkaram

This chapter covers

  • The advantages of having a single pane of glass and its components
  • How different personas can use and benefit from these components
  • Getting some hands-on experience configuring the UI and attaching a cluster to the Anthos UI

We live in a world where application performance is critical for success. To better serve their end users, many organizations have pushed to distribute their workloads from centralized data centers. Whether to be closer to their users, to enhance disaster recovery, or to take advantage of the benefits of cloud computing, this distribution has placed additional pressure on the tooling used to manage and support this strategy. The tools that have flourished under this new paradigm are those that have matured and become more sophisticated and scalable.

There is no one-size-fits-all tool. Likewise, no one person can manage the infrastructure of even a small organization. All applications require tools to manage CI/CD, monitoring, logging, orchestration, deployments, storage, authentication/ authorization, and more. In addition to the scalability and sophistication mentioned earlier, most of the tools in this space offer an informative and user-friendly graphical user interface (GUI). Having an easily understood GUI can help people use the tool more effectively because it lowers the bar for learning the software and increases the amount of pertinent output the user receives.

2.1 Single pane of glass

2.2 Non-Anthos visibility and interaction

2.2.1 Kubernetes Dashboard

2.2.2 Provider-specific UIs

2.2.3 Bespoke software

2.3 The Anthos UI

2.3.1 Fleets

2.3.2 Connect: How does it work?

2.3.3 Installation and registration

2.4 The Anthos Cloud UI

2.4.1 The Anthos dashboard

2.4.2 Service Mesh

2.4.3 Config Management

2.4.4 Clusters

2.4.5 Features