Title
Create new category
Edit page index title
Edit category
Edit link
Configure Kubernetes Metrics Collection Using the PulseNode Agent
Kubernetes metrics collection in Pulse requires cluster-scoped RBAC permissions. Namespace-scoped Role and RoleBinding are not sufficient for Kubernetes metrics retrieval.
Kubernetes metrics require ClusterRole access.
Namespace-scoped RBAC does not enable Kubernetes metrics collection.
Without ClusterRole, Pulse collects only base system metrics.
Configure ServiceAccount, ClusterRole, and ClusterRoleBinding for full Kubernetes observability.
Ensure to deploy the Pulse Node Agent on Kubernetes. For details, see Deploy PulseNode Agent on Kubernetes.
PulseNode collects Kubernetes metrics using cluster-level endpoints such as:
nodes
nodes/stats
nodes/proxy
pods
events
persistentvolumes
persistentvolumeclaims
These endpoints require a ClusterRole and ClusterRoleBinding. Without cluster-level access, Kubernetes API endpoints are not accessible.
Behavior Without ClusterRole
If ClusterRole access is not granted:
Kubernetes metrics (node, pod, event, and volume metrics) are not collected
Namespace-level Kubernetes metrics are not collected
Only base system metrics from the host are collected
The following system metrics are still collected (no Kubernetes RBAC required):
These metrics are collected directly from the host and do not require Kubernetes API access.
Required RBAC Configuration for Full Kubernetes Metrics
To enable Kubernetes metrics collection, configure the following RBAC resources.
For additional help, contact www.acceldata.force.com OR call our service desk +1 844 9433282
Copyright © 2026