Why monitor Kubernetes Namespace?

Namespaces are a way to organize clusters into virtual sub-clusters — they can be helpful when different teams or projects share a Kubernetes cluster. In a scenario where an organization is using a shared Kubernetes cluster for development and production use cases:

• The development team would like to maintain a space in the cluster where they can get a view on the list of Pods, Services, and Deployments they use to build and run their application. In this space, Kubernetes resources come and go, and the restrictions on who can or cannot modify resources are relaxed to enable agile development.

• The operations team would like to maintain a space in the cluster where they can enforce strict procedures on who can or cannot manipulate the set of Pods, Services, and Deployments that run the production site.

Therefore, any unavailability of Pods, Services, or Deployments in the namespaces can adversely impact productivity and business continuity. Thus, continuous monitoring and prompt identification of any abnormalities are very important for continuous delivery of services. eG Enterprise is capable of monitoring Kubernetes/OpenShift cluster out-of-the-box. eG's intelligent agents can instantly detect and promptly alert administrators to issues in the availability, status, and performance of a cluster as a whole and also of individual namespaces. At the same time, these are performance metrics that are specific to Kubernetes/OpenShift cluster and collected at cluster level. However, in an organization that uses a shared Kubernetes cluster, they need performance metrics at namespace level and mostly require to monitor and receive performance metrics related to their respective namespaces. This is where the unique Kuberenetes Namespace monitoring model offered by eG Enterprise comes into play. Using this model, eG monitors specific namespaces that are part of an already existing Kubernetes/OpenShift cluster, proactively detects any abnormalities and reports the same to the respective namespace user community alone.