Closed juangon closed 1 year ago
Interesting, it works the first time I update the Dependent ConfigMap, it happens the second time I update it. I think I don't touch resourceVersion...
Should I increase resourceVersion or something?
Gonna close this issue. It was caused by my wrong code in Updater.update method in dependent resource. Basically I was getting the configmap from the "desired" ConfigMap which has a null resourceVersion.
Bug Report
What did you do?
After implementing the Updater interface in a DependentResource, I see a NulllPointer:
This is in a ConfigMap DependentResource. when updating somewhere else through KubernetesClient edit method it throws this error. When updating the configmap manually it works fine.
What did you expect to see?
No errors
What did you see instead? Under which circumstances?
A NullPointerException
Environment
Kubernetes cluster type:
Vanilla
$ Mention java-operator-sdk version from pom.xml file
4.0.5
$ java -version
11
$ kubectl version
Possible Solution
Additional context