Dependent resources Deployment reconciling repeatedly

[cldfzn]

I'm using the SDK to create a custom resource which creates an ingress, service, and deployment. Similar to the webpage example. However what happens when I run the operator, it creates the resources just fine. It then does not match the desired deployment to the actual deployment and I get thousands of generations of the deployment. When running through the code, it seems like the matcher only prunes managed fields from the actual deployment. When passing a desired state to the SSA matcher, the provided DeploymentBuilder ends up with a few extra empty fields in the converted map and never matches. Am I doing something wrong with this implementation or do I need to somehow prune out all of the extra fields so it matches in the SSA matcher? Or write my own matcher?

[csviri]

Hi @cldfzn , could you pls create a simple reproducer so we can take a look?

It is very hard to figure out without code, and we hade some cases when the implementation of the desired was wrong (like based on actual state). So If you prepare a sample minimalistic project on Github that reproduces it, then we can check it very quickly.

[cldfzn]

Archive.zip

provided a zip file of an example project, after creating a crd instance it goes through generations repeatedly.

[cldfzn]

@csviri out of curiosity, how were you running the operator? did you use a native-image build or gradle or something else?

[csviri]

Was just running it from intellij.

[cldfzn]

Alright, well, that's the root cause of the issue. When I create a native-image from the operator code, this issue occurs. When I create a JVM application, things work as expected.

[csviri]

@cldfzn that makes sense. Could you pls convert this discussion to an issue either in JOSDK or QOSDK, also if you can take a look deeper what is happening would be good help, otherwise we will take a look and fix it eventually

[csviri]

cc @metacosm