The resource-change-monitor component of TCA uses a cache to hold resource changes until the Kubernetes inventory fetches any resource changes. This cache maintains, among other keys and values, the latest resource changes, and the timestamps of these changes. If there is a resource change and the resource is already in the cache, the value will be replaced with the new resource change and the time it was last updated.
If there is a new resource change and it does not exist in the cache, the first check is to confirm if the cache is full. If the cache is full, the entry with the oldest update time will be deleted and the new entry will be inserted to the cache. The Kubernetes inventory service fetches resources changes every 4 minutes.
In TCA 2.1, several bug fixes and improvements to the resource-change-monitor have allowed this component to be more efficient and process events at a higher rate than with previous TCA versions. The increased efficiency of the resource-change-monitor allows it to process close to 1000 resource changes per minute which may be more than the rate at which the Kubernetes inventory service fetches resource changes.
To be addressed in Telco Cloud Automation 2.1.1.