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/v4-4-migration.md
+14-1
Original file line number
Diff line number
Diff line change
@@ -73,4 +73,17 @@ see those
73
73
in [ConfigurationService](https://github.com/java-operator-sdk/java-operator-sdk/blob/e95f9c8a8b8a8561c9a735e60fc5d82b7758df8e/operator-framework-core/src/main/java/io/javaoperatorsdk/operator/api/config/ConfigurationService.java#L268-L289)
74
74
75
75
Note that it is possible to override the related methods/behavior on class level when extending
76
-
the `KubernetesDependentResource`.
76
+
the `KubernetesDependentResource`.
77
+
78
+
### Migration from plain Update/Create to SSA Based Patch
79
+
80
+
Migration to SSA might not be trivial based on the uses cases and the type of managed resources.
81
+
In general this is not a solved problem is Kubernetes. The Java Operator SDK Team tries to follow
82
+
the related issues, but in terms of implementation this is not something that the framework explicitly
83
+
supports. Thus, no code is added that tries to mitigate related issues. Users should thoroughly
84
+
test the migration, and even consider not to migrate in some cases (see feature flags above).
85
+
86
+
See some related issues in [kubernetes](https://github.com/kubernetes/kubernetes/issues/118725) or
87
+
[here](https://github.com/keycloak/keycloak/pull). Please create related issue in JOSDK if any.
0 commit comments