{"id":19417,"date":"2019-06-12T10:01:15","date_gmt":"2019-06-12T08:01:15","guid":{"rendered":"https:\/\/www.centreon.com\/superviser-kubernetes-et-docker-avec-centreon\/"},"modified":"2023-12-22T10:48:47","modified_gmt":"2023-12-22T09:48:47","slug":"superviser-kubernetes-et-docker-avec-centreon","status":"publish","type":"post","link":"https:\/\/www.centreon.com\/fr\/superviser-kubernetes-et-docker-avec-centreon\/","title":{"rendered":"Superviser Kubernetes et Docker avec Centreon"},"content":{"rendered":"

Dans ce tutoriel, nous d\u00e9crirons comment Centreon peut superviser des conteneurs Docker orchestr\u00e9s au sein d\u2019un cluster Kubernetes.<\/strong><\/p>\n

Kubernetes est la solution d’orchestration de conteneurs en production la plus r\u00e9pandue pour le d\u00e9ploiement d’applications et de microservices conteneuris\u00e9s. Et Prometheus s\u2019av\u00e8re pratique en tant qu\u2019unique point de collecte et d\u2019agr\u00e9gation de mesures pour les trois niveaux de votre environnement microservice : les n\u0153uds Kubernetes individuels, le cluster Kubernetes et les applications.<\/span><\/p>\n

Dans cet article de blog, nous montrerons comment les plugins et Plugin Packs Centreon permettent de faciliter la supervision d\u2019un cluster Kubernetes via un serveur Prometheus. Nous commencerons par introduire Kubernetes et Prometheus. Puis, nous installerons et testerons le plugin Kubernetes. Enfin, nous montrerons comment utiliser le Plugin Pack pour superviser un cluster Kubernetes avant de pr\u00e9ciser les diff\u00e9rentes m\u00e9triques disponibles sur la plateforme Centreon.<\/span><\/p>\n

** La suite de cet article et le tutoriel sont r\u00e9dig\u00e9s en anglais **<\/i><\/p>\n

\"\"
Kubernetes Architecture Diagram – By Khtan66<\/a> – Own work, CC BY-SA 4.0<\/span><\/figcaption><\/figure>\n

1. A quick introduction about Kubernetes and Prometheus<\/span><\/h2>\n

Kubernetes<\/strong> is an open-source orchestration system for automating application deployment, scaling, and, management running in a containerized environment. Its development and design are heavily influenced by Google’s Borg system, referring to the character Seven of Star Trek TV show, which also explains the seven spokes on the wheel of the Kubernetes logo. It is now maintained by the Cloud Native Computing Foundation.<\/p>\n

It consists of multiple complementary primitives that allow Kubernetes to automatically administer the lifecyle of containerized applications across a cluster of nodes.<\/p>\n

The key objects are:<\/p>\n\n\n\n\n\n
Nodes, Clusters and Namespaces<\/strong><\/td>\nNodes are physical or virtual machines running multiple Docker containers. A Cluster is made of a master node which orchestrate applications and multiple worker nodes who execute them. Namespaces are virtual clusters backed by a physical cluster.<\/td>\n<\/tr>\n
Pods & Containers<\/strong><\/td>\nThe basic scheduling unit in Kubernetes is a\u00a0pod. It adds a higher level of abstraction by grouping containerized components. A pod consists of one or more containers that are guaranteed to be co-located on the host machine and can share resources.<\/td>\n<\/tr>\n
Deployments, Replica Sets, Daemonsets\u00a0<\/strong><\/td>\nDeployments specify how to execute and operate an application. Deployments scale up and down pods and Replica Sets to reach a desired state<\/em> for the application. Replica Sets orchestrate pod creation, updates and deletion. Daemonsets are used for background tasks or daemons that must run on all nodes: when adding a node to a cluster, the pods in a Daemonset are automatically started on that node.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

 <\/p>\n

Prometheus<\/strong> is an open-source Time-Series Database (TSDB) and\u00a0a graduated project of the Cloud Native Computing Foundation, along with Kubernetes. Several assets makes it convenient to monitor microservices in a Kubernetes environment:<\/p>\n