Skip to content

Commit 15d50a9

Browse files
shawkinsmetacosm
andauthored
Update docs/documentation/dependent-resources.md
Co-authored-by: Chris Laprun <metacosm@users.noreply.github.com>
1 parent 271dae3 commit 15d50a9

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/documentation/dependent-resources.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -370,7 +370,7 @@ server. To bypass the matching feature completely, simply override the `match` m
370370
return `false`, thus telling JOSDK that the actual state never matches the desired one, making
371371
it always update the resources using SSA.
372372

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 - leading to indefinite reconciliation. 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 on an older Kubernetes version, consider changing your desired state, turning off SSA for that resource, or even upgrading your Kubernetes version. If you encounter it on a newer Kubernetes version, please log an issue with the JOSDK and with upstream Kubernetes.
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 - leading to infinite reconciliations. 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 on an older Kubernetes version, consider changing your desired state, turning off SSA for that resource, or even upgrading your Kubernetes version. If you encounter it on a newer Kubernetes version, please log an issue with the JOSDK and with upstream Kubernetes.
374374

375375
## Telling JOSDK how to find which secondary resources are associated with a given primary resource
376376

0 commit comments

Comments
 (0)