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
The only thing needs to be done is to extend the `CRUKubernetesDependentResource` and specify the desired state.
128
+
Note that it is `CRU` instead of `CRUD`, since it not explicitly manages the delete operation. That is handled by
129
+
the Kubernetes garbage collector through owner references, what is automatically set to the resource.
130
+
`CRUKubernetesDependentResource` is only an adaptor class that already implements the`Creator` and `Updater` but
131
+
not the `Deleter` interface.
132
+
133
+
See the full source code [here](https://github.com/java-operator-sdk/java-operator-sdk/blob/main/sample-operators/webpage/src/main/java/io/javaoperatorsdk/operator/sample/DeploymentDependentResource.java).
134
+
97
135
## Managed Dependent Resources
98
136
99
137
As mentioned previously, one goal of this implementation is to make it possible to semi-declaratively create and wire
@@ -211,7 +249,7 @@ public class WebPageStandaloneDependentsReconciler
211
249
212
250
There are multiple things happening here:
213
251
214
-
1. Dependent resources are explicitly created, and can be access later by reference.
252
+
1. Dependent resources are explicitly created and can be access later by reference.
215
253
2. Event sources are produced by the dependent resources, but needs to be explicitly registered in this case.
216
254
3. Reconciliation is called explicitly, but here the workflow customization is fully in the hand of the developer.
217
255
4. Status is set in a different way, this is just an alternative way to show, that the actual state can be read using
Copy file name to clipboardExpand all lines: sample-operators/webpage/src/main/java/io/javaoperatorsdk/operator/sample/DeploymentDependentResource.java
0 commit comments