You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/documentation/features.md
+11-1Lines changed: 11 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -713,7 +713,17 @@ See also an example implementation in the
713
713
714
714
## Optimization of Caches
715
715
716
-
Incase of large clusters with huge amount of resources the memory consumption of an operator
716
+
Incase of large clusters with huge amount of resources the memory consumption of an operator.
717
+
In order to reduce the memory consumption both primary and secondary resources in cache can be pruned, thus only
718
+
partial objects will remain in memory.
719
+
720
+
This has some implications regarding how those objects needs to be managed within a reconciler. Since from this point
721
+
reconciler will work only from partial object, all the updates on the pruned resources needs to be done by a PATCH
722
+
operations, thus just to send only the required changes.
723
+
724
+
To see how to use, and how to handle related caveats regarding patches what utilizes
725
+
[server side apply](https://kubernetes.io/docs/reference/using-api/server-side-apply/) check the provided
726
+
[integration test](https://github.com/java-operator-sdk/java-operator-sdk/blob/c688524e64205690ba15587e7ed96a64dc231430/operator-framework/src/test/java/io/javaoperatorsdk/operator/CachePruneIT.java) and reconciler.
0 commit comments