-
Notifications
You must be signed in to change notification settings - Fork 227
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
DIFF does not seem to work in case of CRD version upgrade #2551
Comments
I can reproduce this in a small experiment: https://github.com/manno/fleet-experiments/blob/main/crd-versioning/crds/crd-versions.yaml |
I was missing the namespace on my
However, the bundle name is After adapting the bundle names, the deployments eventually succeed.
It might be easier to match with a selector. |
@Martin-Weiss can you check the release names in your |
@manno - thanks for checking - for some reason I can not reproduce the problem, anymore.. so it seems the issue is gone on its own.. Will close and re-open in case we see it, again. |
Is there an existing issue for this?
Current Behavior
We deploy open-telemetry and kubewarden via fleet. In kubewarden-app bundle we get "modified" and we can not get a diff working. Assuption is that this happens because fleet deploys v1alpha1 CRD via helm chart for kubewarden-controller but kubernetes switches the object to v1beta1 - so the diff does not match properly.
See https://github.com/Martin-Weiss/rancher-fleet/blob/main/kubewarden/app/fleet.yaml#L12 - this diff does not work.
Expected Behavior
The diff should work regardless of CRD version changes
Steps To Reproduce
Try to create a proper diff to get rid of "modified".
Environment
Logs
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: