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/dependent-resources.md
+2
Original file line number
Diff line number
Diff line change
@@ -370,6 +370,8 @@ server. To bypass the matching feature completely, simply override the `match` m
370
370
return `false`, thus telling JOSDK that the actual state never matches the desired one, making
371
371
it always update the resources using SSA.
372
372
373
+
WARNING: Older versions of Kubernetes before 1.25 would create an additional resource version for every SSA update performed with certain resources - even though there were no actual changes in the stored resource. This behavior was seen with Secrets using stringData, Ingresses using empty string fields, and StatefulSets using volume claim templates. The operator framework has added built-in handling for the StatefulSet issue. If you encounter this issue, consider changing your desired state, turning off SSA for that resource, or even upgrading your Kubernetes version.
374
+
373
375
## Telling JOSDK how to find which secondary resources are associated with a given primary resource
Copy file name to clipboardExpand all lines: operator-framework-core/src/main/java/io/javaoperatorsdk/operator/processing/dependent/kubernetes/DesiredResourceSanitizer.java
Copy file name to clipboardExpand all lines: operator-framework-core/src/main/java/io/javaoperatorsdk/operator/processing/dependent/kubernetes/KubernetesDependentResource.java
+3-7
Original file line number
Diff line number
Diff line change
@@ -114,7 +114,6 @@ public R create(R desired, P primary, Context<P> context) {
Copy file name to clipboardExpand all lines: operator-framework-core/src/main/java/io/javaoperatorsdk/operator/processing/dependent/kubernetes/SSABasedGenericKubernetesResourceMatcher.java
0 commit comments