@@ -711,30 +711,6 @@ setting, where this flag usually needs to be set to false, in order to control t
711
711
See also an example implementation in the
712
712
[WebPage sample](https: // github.com/java-operator-sdk/java-operator-sdk/blob/3e2e7c4c834ef1c409d636156b988125744ca911/sample-operators/webpage/src/main/java/io/javaoperatorsdk/operator/sample/WebPageOperator.java#L38-L43)
713
713
714
- ## Optimization of Caches
715
-
716
- ** Cache pruning is an experimental feature. Might a subject of change or even removal in the future. **
717
-
718
- Operators using informers will initially cache the data for all known resources when starting up
719
- so that access to resources can be performed quickly. Consequently , the memory required for the
720
- operator to run and startup time will both increase quite dramatically when dealing with large
721
- clusters with numerous resources.
722
-
723
- It is thus possible to configure the operator to cache only pruned versions of the resources to
724
- alleviate the memory usage of the primary and secondary caches. This setup, however, has
725
- implications on how reconcilers deal with resources since they will only work with partial
726
- objects. As a consequence, resources need to be updated using PATCH operations only, sending
727
- only required changes.
728
-
729
- To see how to use, and how to handle related caveats regarding how to deal with pruned objects
730
- that leverage
731
- [server side apply](https: // kubernetes.io/docs/reference/using-api/server-side-apply/) patches,
732
- please check the provided
733
- [integration test](https: // github.com/java-operator-sdk/java-operator-sdk/blob/c688524e64205690ba15587e7ed96a64dc231430/operator-framework/src/test/java/io/javaoperatorsdk/operator/CachePruneIT.java)
734
- and associates reconciler.
735
-
736
- Pruned caches are currently not supported with the Dependent Resources feature.
737
-
738
714
## Automatic Generation of CRDs
739
715
740
716
Note that this feature is provided by the
0 commit comments