status.observedGeneration field violates type convention
Checklist:
- [x] I've included steps to reproduce the bug.
- [x] I've included the version of argo rollouts.
Describe the bug
Interactions with the status.observedGeneration field on Rollouts behave unexpectedly because the field is forced to be a string rather than an integer on the CRD. This leads to incompatibilities with tooling which observe that field to ensure state of an object. This is particularly frustrating when trying to use Rollouts resources with FluxCD.
To Reproduce
- Create a Rollout
- Get the Rollout from the API
- Observe that the value of status.observedGeneration is in quotes
Expected behavior
The status.observedGeneration field should be an integer in the CRD and represented internally in the controller code as an int64, matching convention of upstream.
Screenshots
N/A
Version
1.6.6
Logs
No relevant logs.
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritize the issues with the most 👍.
I am asking to fix it, almost the half a year passed - no motion and another colleague was hit by this bug:
https://cloud-native.slack.com/archives/CLAJ40HV3/p1728910929113889
FWIW, I submitted a PR here #4384
Hello, is there a planned date for the 1.9 version ? We have the same issue with FluxCD 😅