Suppressing frequent changes in Kubernetes clusters reported by "CNO for visibility"What is the Suppression of Frequent Changes? CNO for Visibility (a.k.a informer) is reporting in near real-time to the ServiceNow instance on changes that happen in the Kubernetes cluster. However, certain changes in the clusters are happening repeatedly and frequently. Reporting on those changes can create a load on the instance, and does not add any value. A few examples of such changes: A CronJob configured to run every minute will create a new Job and Pod every minute and delete them later onA pod that fails to start because of some problem (e.g. fails to pull an image) will see a frequent changes in its statusWhen a container is crashing and restarted because of a frequent problem CNO for Visibility can ignore changes on Kubernetes resources that happen in a rate the exceeds a configured threshold. Turning Off the Feature The feature is enabled by default but can be turned off by users: When installing using Helm chart, use the command line argument --set suppressFrequentChanges=false to disable the feature. When using the Kubernetes Yaml file, change the value of the environment variable SUPPRESS_FREQUENT_CHANGES to false The Change Rate Threshold When the suppression feature is turned on, CNO for visibility will suppress changes that happen in a rate of more than 0.15 time minute (roughly more frequent than every 7 minutes). This threshold can be controlled by users. When installing using Helm chart, use the command line argument --set suppressChangesRatePerMin=<Number in float format> to set the desired threshold. When using the Kubernetes Yaml file, change the value of the environment variable SUPPRESS_CHANGES_RATE_PER_MIN to the desired value in float format.