docs

Signed-off-by: Attila Mészáros <csviri@gmail.com>

Author: csviri

docs/documentation/v5-0-migration.md

@@ -17,3 +17,6 @@ permalink: /docs/v5-0-migration
    [`EventSourceUtils`](https://github.com/operator-framework/java-operator-sdk/blob/main/operator-framework-core/src/main/java/io/javaoperatorsdk/operator/api/reconciler/EventSourceUtils.java#L11-L11)
    now contains all the utility methods used for event sources naming that were previously defined in
    the `EventSourceInitializer` interface.
+3. Patching status through `UpdateControl` like the `patchStatus` method now by default
+   uses Server Side Apply instead of simple patch. To use the former approach, use the feature flag 
+   in [`ConfigurationService`](https://github.com/operator-framework/java-operator-sdk/blob/main/operator-framework-core/src/main/java/io/javaoperatorsdk/operator/api/config/ConfigurationService.java#L400-L400)

operator-framework-core/src/main/java/io/javaoperatorsdk/operator/api/config/ConfigurationService.java

@@ -392,7 +392,10 @@ default boolean parseResourceVersionsForEventFilteringAndCaching() {
   }
 
   /**
-   * {@link io.javaoperatorsdk.operator.api.reconciler.UpdateControl} patchStatus
+   * {@link io.javaoperatorsdk.operator.api.reconciler.UpdateControl} patchStatus can either use
+   * simple update or SSA for status subresource patching.
+   *
+   * @return true by default
    */
   default boolean useSSAForResourceStatusPatch() {
     return true;