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: operator-framework-core/src/main/java/io/javaoperatorsdk/operator/processing/dependent/kubernetes/GenericKubernetesResourceMatcher.java
+17-17Lines changed: 17 additions & 17 deletions
Original file line number
Diff line number
Diff line change
@@ -73,26 +73,26 @@ public Result<R> match(R actualResource, P primary, Context<P> context) {
73
73
* @param labelsAndAnnotationsEquality if true labels and annotation match exactly in the actual
74
74
* and desired state if false, additional elements are allowed in actual annotations.
75
75
* Considered only if considerLabelsAndAnnotations is true.
76
-
* @param specEquality if {@code false}, the algorithm checks if the properties in the desired
77
-
* resource spec are same as in the actual resource spec. The reason is that admission
78
-
* controllers and default Kubernetes controllers might add default values to some
79
-
* properties which are not set in the desired resources' spec and comparing it with simple
80
-
* equality check would mean that such resource will not match (while conceptually should).
81
-
* However, there is an issue with this for example if desired spec contains a list of
82
-
* values and a value is removed, this still will match the actual state from previous
83
-
* reconciliation. Setting this parameter to {@code true}, will match the resources only if
84
-
* all properties and values are equal. This could be implemented also by overriding equals
85
-
* method of spec, should be done as an optimization - this implementation does not require
86
-
* that.
76
+
* @param valuesEquality if {@code false}, the algorithm checks if the properties in the desired
77
+
* resource spec (or other non metadata value) are same as in the actual resource spec. The
78
+
* reason is that admission controllers and default Kubernetes controllers might add
79
+
* default values to some properties which are not set in the desired resources' spec and
80
+
* comparing it with simple equality check would mean that such resource will not match
81
+
* (while conceptually should). However, there is an issue with this for example if desired
82
+
* spec contains a list of values and a value is removed, this still will match the actual
83
+
* state from previous reconciliation. Setting this parameter to {@code true}, will match
84
+
* the resources only if all properties and values are equal. This could be implemented
85
+
* also by overriding equals method of spec, should be done as an optimization - this
Copy file name to clipboardExpand all lines: operator-framework-core/src/test/java/io/javaoperatorsdk/operator/processing/dependent/kubernetes/GenericKubernetesResourceMatcherTest.java
0 commit comments