-
Bug
-
Resolution: Done
-
Normal
-
ACM 2.9.0
-
False
-
None
-
False
-
-
-
Low
-
No
Provide info for the following steps:
1. - [ ] Mandatory Add the required version to the Fix version/s field.
We can document this just in ACM 2.9 but it applies also to ACM 2.6+
https://access.redhat.com/documentation/de-de/red_hat_advanced_cluster_management_for_kubernetes/2.8/html-single/governance/index
2. - [ ] Mandatory Choose the type of documentation change.
- [ ] Update to an existing topic
3. - [ ] Mandatory for GA content:
4. - [ ] Mandatory for bugs: What is the diff? Clearly define what the problem is, what the change is, and link to the current documentation:
We document spec.evaluationInterval.compliant Optional Used to define how often the policy is evaluated when it is in the compliant state. The values must be in the format of a duration which is a sequence of numbers with time unit suffixes. For example, 12h30m5s represents 12 hours, 30 minutes, and 5 seconds. It can also be set to never so that the policy is not reevaluated on the compliant cluster, unless the policy spec is updated. spec.evaluationInterval.noncompliant
But we do not document the default value.
It is:
Configuration Policies are evaluated roughly every 10 seconds when the evaluation interval is not set. This can be longer if the Configuration Policy controller is saturated on the managed cluster.
Maybe “minimum time between evaluations” is a more accurate phrase