Shulou(Shulou.com)06/03 Report--

Over the past decade, I have been working in virtualization and cloud computing, leading product management at VMware, Mercury Interactive, and Oracle, with a particular focus on DevOps. Until 2014, I began to pay close attention to and study containers. When Kubernetes was launched to the public in 2015, I felt strongly that companies needed an easier way to deploy containers in their internal environment. At that time, I founded Qubeship.io, a CI / CD tool that provides enterprise-class containers. However-- despite our best efforts to deal with this problem-- managing Kubernetes clusters remains a huge challenge.

Rancher, on the other hand, solved this complex problem. From the original container orchestration engine, it has rapidly developed into a multi-cluster, multi-tenant Kubernetes management platform, and solved the problem of thousands of enterprises around the world landing Kubernetes in an important production environment.

Rancher 2.2 has further promoted this development. Many new features and bug fixes will be included in Rancher 2.2, which I will focus on in this article:

New Alpha release process

Out-of-the-box monitoring solution for clusters managed by Rancher.

Alpha version release process

Starting with Rancher 2.2.0, Rancher Labs plans to release a series of alpha versions before the final 2.2 GA release. This will give users enough time to experiment with new features and help identify potential problems.

The Alpha version is undoubtedly the latest and most cutting-edge, and it may include new features, enhancements, and bug fixes. However, we do not recommend that users deploy any version of alpha in a production environment, and Rancher does not provide testing or support for upgrading to or from the alpha version.

If there are some particularly noteworthy features or fixes in a particular version of alpha, we will highlight them in release note. We will also mark important known issues. We will try to be as detailed as possible, but this list is not exhaustive.

We very much hope that you can provide your feedback / comments / suggestions to the Rancher team when using the alpha version as much as possible, which is also a great way to help us optimize the product to the maximum extent before the product is officially GA!

Cool techs monitored by Prometheus in Multi-Cluster and Multi-tenant Environment

Rancher Labs has officially announced the introduction of milestone-level enhanced support for Prometheus in Rancher 2.2 to enhance the visibility of all Kubernetes clusters while ensuring isolation between different projects and users. As a result, Rancher is the only solution that supports Prometheus in a multi-cluster, multi-tenant environment. In Rancher 2.2, using Prometheus to monitor the Kubernetes environment managed by Rancher requires only two steps:

Select Cluster

Start the monitoring with one click

Got it!

We can do this because Rancher 2.2 is equipped with fully integrated Prometheus and Grafana.

Use the tutorials:

Log in and select the cluster you want to monitor. It is important to note that CPU utilization, memory utilization, and Pods charts show the current state of the system. Although these indicators are useful, they only show what is happening now.

Click the tools tab and select the Monitoring option.

Click the Prometheus button. With regard to data retention and ports, you can use the default configuration.

With regard to storing Prometheus and Grafana data, there is also an option to add persistent storage. If you want to enable it, select it now. In this demonstration in this article, I did not select them.

Save your changes.

Navigate back to the cluster, and you can see more other content, including cluster metrics, Etcd metrics, Kubernetes component metrics, and Rancher log metrics.

After expanding each indicator, you can see a new layer of indicators under the indicator. Hover your mouse over the chart and you can see more information about the letter.

Using the time series drop-down list, you can further zoom in and see how the system's performance changes over different periods of time.

Click the Grafana icon to view the dashboard:

Let's take a look at project-level monitoring.

Project-level monitoring

In Rancher, projects are a powerful way for multiple teams to have their own multi-tenant workspaces (or projects) on the same cluster.

Select the project with the workload and navigate to the tool → monitoring. If monitoring is not already enabled, you can select the Prometheus monitoring button to enable it.

Navigate back to the Workload tab and expand the "Workload Metrics" section now available to view all utilization and I / O metrics. Hover over any chart for more details, and use the time series drop-down list to further zoom in and view a specific time period.

You can also continue to delve deeper into Pod and even container-level metrics. You can view Pod metrics and container metrics by clicking on the component you want to observe, and then following the same steps as above.

Conclusion theory

I hope that through this article, you can learn how to easily and quickly monitor a multi-Kubernetes cluster and multi-tenant environment through the out-of-the-box Prometheus and Grafana monitoring solutions in Rancher 2.2.

There are several Alpha versions available for you to try out. For more information, please see here:

Https://github.com/rancher/rancher/releases

As always, we look forward to your feedback. The beta version of the product will be available to you soon, the GA time is scheduled for early 2019, please stay tuned!

Keep Rancher-ing!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.