Skip to main content

​
Collectors: The Essence of Data Collection

In Plerion Kubernetes Security Posture Management (KSPM), collectors systematically gather Kubernetes artifacts, metrics, and events. This precise data collection is essential for organizing information before processing by the Plerion KSPM Control Plane, enhancing overall security and compliance in a Kubernetes environment.

​
The Significance of “Collector-Manager”

The term “collector-manager” emphasizes the versatile role of this Kubernetes operator. It coordinates and oversees various collectors, each assigned specific data collection tasks. This approach provides a unified solution for managing Kubernetes security and compliance effectively.

​
High Availability: A Crucial Imperative

The collector-manager is designed to be highly available, and is configured with redundancy by deploying multiple replicas initially for a robust fail-safe mechanism. The controller pod receives the highest scheduling priority, identified by the priorityClassName system-cluster-critical. This setup reflects our commitment to enhancing reliability and resilience, meeting the demanding standards of the Plerion KSPM platform.

​
Supported Kubernetes Distributions

The Plerion Collector Manager is designed to seamlessly integrate with a variety of Kubernetes distributions, ensuring its adaptability to different cloud and infrastructure environments. Below is a list of some major Kubernetes distributions that are officially supported:
  1. AWS Elastic Kubernetes Service (EKS)
  2. On-Premises Kubernetes Clusters

​
Supported Node Architectures

The collector-manager image runs on amd64 (x86-64) and arm64 nodes. It is published as a multi-architecture image, so your cluster pulls the variant matching each node and no nodeSelector is required on a cluster that mixes both.

​
Permissions for Resource Collection

The Collector Manager Helm chart installs read-only permissions for Kubernetes resource interaction. These permissions allow the collectors to retrieve Kubernetes artifacts, metrics, and events, facilitating the identification of potential misconfigurations. For a detailed breakdown, please refer to this guide.