New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replacing ingress with createOrReplace ignores changes to annotations #2312
Comments
Related to #2292 |
@rohanKanojia Do you expect the related ticket to fix this issue? |
Umm, yeah. We're planning to refactor behavior of |
Great! I've worked around it for now with a delete and apply, but this is less than ideal in case DNS decides to propagate the delete and not the create due to the timing of the ingress creation. Do you have an idea of when #2292 might be picked up? |
It's already in our Sprint backlog: https://github.com/eclipse/jkube/projects/6 . We would try it pick it whenever we can. |
I think this issue should be fixed via #2372 , I've added a test for this case here: Lines 206 to 229 in 14cae94
|
Closing this issue. But feel free to reopen if it doesn't work for you or you face any other problems. |
Hi guys,
I am replacing Kubernetes resources with
client.resourceList(yaml).inNamespace(namespace).createOrReplace()
, but my ingresses do not get replaced when only the annotations have changed. I use this for example to set/unset thenginx.ingress.kubernetes.io/whitelist-source-range
annotation.It looks like
ResourceCompare#equals
compares only labels, and not annotations.Is this intentional, and do I need to work around this, or is this a bug?
The text was updated successfully, but these errors were encountered: