Received event after patch using @EnableMockOperator

[jmformenti]

I found a weird behaviour creating a test using @EnableMockOperator.

When I return the control using patchStatus:

return UpdateControl.patchStatus(resource);

I receive immediately a new event for that resource, but if I'm not wrong, this is not the behaviour expected. I mean in a real Kubernetes cluster after patchStatus I don't receive a new event for that resource.

In the other hand, if I use updateStatus with @EnableMockOperatorit works fine, I mean I don't receive a new event.

[csviri]

Hi @jmformenti
this seems to be an issue in mock server. Pls create an issue in Fabric8 Client:
https://github.com/fabric8io/kubernetes-client

Since the mock server is implemented there.
thank you!

[jmformenti]

Hi Attila
Even a patch was submitted to kubernetes-client, I still have the same issue.
In the issue opened in kubernetes-client (fabric8io/kubernetes-client#4478), there is this quote:

Unless the mock server is made aware of the nullable / defaulting behavior - https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/#defaulting-and-nullable we don't be able to handle this robustly on the mock side.

Does it make sense for you?

[jmformenti]

Oh, my bad, there was a stupid mistake on my side.
Now it's working fine 👍