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: docsy/content/en/blog/releases/v5-release.md
+15-3Lines changed: 15 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,16 +5,17 @@ weight: 10
5
5
6
6
# Version 5.0.0-RC1 Released!
7
7
8
-
We've just released the next major version of Java Operator SDK. There are many goals for this release. Instead, it is
9
-
a collection of improvements and features that require API changes. In this post, we will review the significant changes,
8
+
We've just released the next major version of Java Operator SDK. There is not a single big feature or goal of this release. Instead, it is
9
+
a collection of improvements and features that require API changes. However, the following improvements made the framework much easier to use and understand.
10
+
In this post, we will review all the significant changes,
10
11
explain their rationale, and show how to migrate from the previous release if needed.
11
12
12
13
## Changes
13
14
14
15
### SSA for status patch and finalizer adding
15
16
16
17
[Server Side Apply](https://kubernetes.io/docs/reference/using-api/server-side-apply/) has already been supported for a long time
17
-
in the fabric8 client and features like dependent resources. However, it is not used by default
18
+
in the fabric8 client, and features like dependent resources. However, it is not used by default
18
19
to update the status of the custom resource with the `UpdateControl` patch operations in the reconciler and to
19
20
add the finalizer for the custom resource.
20
21
@@ -30,6 +31,17 @@ Also, the related [workaround](https://github.com/operator-framework/java-operat
30
31
31
32
See [related issue](https://github.com/operator-framework/java-operator-sdk/issues/1931).
32
33
34
+
### Removal of automatic observed generation handling
35
+
36
+
The `ObservedGenerationAware` interface and `ObservedGenerationAwareStatus` and related functionality were removed.
37
+
Although this feature allowed us to handle observed generation in status easily,
38
+
the rationale behind this removal is that it is not possible to implement it elegantly when using SSA. Also,
39
+
it is trivial to implement it manually.
40
+
41
+
See the related integration test for how to do it manually [here](https://github.com/operator-framework/java-operator-sdk/blob/main/operator-framework/src/test/java/io/javaoperatorsdk/operator/sample/manualobservedgeneration/ManualObservedGenerationReconciler.java).
42
+
43
+
See [related issue](https://github.com/operator-framework/java-operator-sdk/issues/2329).
44
+
33
45
### Removal of EventSourceInitializer interface
34
46
35
47
`EventSourceInitializer` is an interface that was implemented by most of the reconcilers. In general
0 commit comments