documentation updates for opa/cache

docs/docs/cache.md

@@ -84,4 +84,6 @@ If you use `force_cache`, please note this overrides cache directives defined by
     If you are using cache settings in policies it is strongly recommended to consider using these OPA config settings(not in Rego).
 - `caching.inter_query_builtin_cache.max_size_bytes` to set a Inter-query cache size limit in bytes. OPA will drop old items from the cache if this limit is exceeded. By default, no limit is set (i.e. unlimited) and this could cause Out of Memory `OOMKilled` and `MemoryPressure` issues.
 - `caching.inter_query_builtin_cache.forced_eviction_threshold_percentage` - Threshold limit configured as percentage of caching.inter_query_builtin_cache.max_size_bytes, when exceeded OPA will start dropping old items permaturely. By default, set to 100.
-- `caching.inter_query_builtin_cache.stale_entry_eviction_period_seconds` - Stale entry eviction period in seconds. OPA will drop expired items from the cache every stale_entry_eviction_period_seconds. By default, set to 0 indicating stale entry eviction is disabled.
\ No newline at end of file
+- `caching.inter_query_builtin_cache.stale_entry_eviction_period_seconds` - Stale entry eviction period in seconds. OPA will drop expired items from the cache every stale_entry_eviction_period_seconds. By default, set to 0 indicating stale entry eviction is disabled.
+
+See [sizing](sizing)

docs/docs/opa.md

@@ -11,11 +11,13 @@
 |-----------|---------------------------------------|
 | M18       | v0.54 or later                        |
 | M21       | v0.56 or later                        |
-| M22       | v0.62.1 or later                      |
-| M23       | v0.62.1 or later                      |
-| M24       | v0.67.1 or later                      |
+| M22       | v0.68.0 or later*                     |
+| M23       | v0.68.0 or later                      |
+| M24       | v0.68.0 or later                      |
 | M25       | v0.68.0 or later                      |
 
+M22 - OPA v0.67.1 has been reported to work well, but general recommendation will be to update this to v0.68.0
+
 ## Role
 - Currently Policy Service is not compatible with OPA version 1.x syntax, so do not use the `-v1-compatible` flag.
 In M20, Policy Service now has the ability to update OPA for the purpose of adding additional data partitions.

docs/docs/sizing.md

@@ -29,8 +29,8 @@ minReplicas should always be 3 or more in production environments or preship env
 
     Smaller CPU and memory requests sizes should work, however under load you may experience slow downs and other performance issues.
 
-- For OPA minimum sizing cpu requests 500M, memory 256Mi and 2 pods.
-- Recommended is 1000M CPU and 1000Mi RAM.
-- Recommend to use less than 400000000 max_size_bytes setting for the OPA cache with 1000Mi memory.
-- Horizontal Pod Autoscaling (HPA) is recommended and minReplicas should always be 2 or more in production environments and pre-ship environments.  It has been reported that 1000M CPU, 1000Mi Memory requests and a minimum of 3 pods works well under load.
-- The number of OPA pods should be *at least* half the number of policy service pods. i.e. if you have 6 policy pods, you should have 3 OPA pods.
\ No newline at end of file
+- For OPA minimum sizing cpu requests 500M, memory 500Mi and 2 pods. However this should never be used in production.
+- Recommended is 1000M CPU and 1000Mi memory request and 1200Mi memory limit. However be sure to size this for your workload and policies. For example if you use caching you may want to adjust these higher.
+- Recommend to use less than 40% of memory request as `caching.inter_query_builtin_cache.max_size_bytes`. For example use 400000000 `caching.inter_query_builtin_cache.max_size_bytes` setting for the OPA cache with 1000Mi memory request size. Be sure to size for your workload and policies.
+- Horizontal Pod Autoscaling (HPA) is recommended and minReplicas should always be 2 or more in production environments and pre-ship environments.  It has been reported that 1000M CPU, 1000Mi Memory Requests, 2000Mi Memory Limit and a minimum of 3 pods works well under load but under certain conditions you may need more resources.
+- The number of OPA pods should be *at least* half the number of policy service pods. i.e. if you have 6 policy pods, you should have min. 3 OPA pods.