RealTheory provides real-time visibility into metrics, cost, performance, and health data for Kubernetes environments. Nearly all of this data comes from a small but critical component called the RealTheory Collector.
The Collector deployment manifest, which can be easily generated with the correct configuration settings through the RealTheory console:
latest tag.imagePullPolicy configuration to Always, instructing Kubernetes to always check for and pull the latest image version on pod restart.The Collector itself:
This design ensures that the Collector is always in sync with the RealTheory services API and that your cluster data is continuously collected and displayed in the console without manual intervention.
If the Collector cannot auto-upgrade or connect properly to RealTheory services, the platform will be unable to ingest new metrics from the affected cluster. This results in:
In many cases, this problem can be traced to changes made to the Collector deployment before it’s applied to the cluster, such as:
latest tag.These changes break the intended auto-upgrade process. If the alternate registry is not regularly updated to match the official RealTheory registry, or if the Collector is pinned to an outdated version, it will eventually fall out of compatibility with the RealTheory service layer—potentially breaking functionality or preventing access to new features.
To maintain accurate, real-time cluster data in the console:
imagePullPolicy, which must remain set to Always.Important: Any modification to the Collector’s image path or imagePullPolicy is unsupported and will disrupt data collection, even if intended to solve caching or registry access issues.
On This Page
Search for a command to run...