Attila Mészáros
Attila Mészáros
I think this is kinda gray area, it's not a bug fix, rather an improvement IMHO. But fine with merging it to the main, and have a release.
merged to main, thank you @honnix !!
We don't have a Job specific matcher yet, but this can be probably just fixed if you override the matcher. What is your exact use case? Asking because recreating a...
Ahh ok, this is defintely should be possible to do even now, just overriding the match and the update function. However might be easier if the desired would receive the...
@andreaTP I linked a PR, we can discuss that. Basically now this is possible just more hacky, with that it should be doable much more elegantly. Probably the best would...
Probably related to this issue: https://github.com/java-operator-sdk/java-operator-sdk/issues/1405
yep: https://github.com/java-operator-sdk/java-operator-sdk/blob/2cb616c4c4fd0094ee6e3a0ef2a0ea82173372bf/operator-framework/src/test/java/io/javaoperatorsdk/operator/InformerRelatedBehaviorITS.java @andreaTP it is a little special, since it is not trivial to test. See javadocs on the test class.
An other thing we should check in the probes if the informers are watching: https://github.com/fabric8io/kubernetes-client/issues/4340#issuecomment-1222394149 So probably the operator is not ready if the informers are not watching. But this...
After thinking more of this issue, there is a serious problem when an informer is not working. The caches are not populated with the fresh resources, so until the RBAC...
For the case when dynamically adding watched namespaces, there could be some optimizations, like reconcile a resource only when all the informers watching resources from a namespaces are healthy. But...