Fixed status updated only when Kafka instance ready with no updating #472
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When a Strimzi version upgrade is started by changing the
spec.versions.strimzi
in the ManagedKafka resource, the correspondingstatus.versions.strimzi
field should still report the older one while the upgrade is in process so when the StrimziUpdating condition is still true.Currently, there is a bug with fleetshard operator reporting the new Strimzi version in the status while the updating is still in progress; the status field should be updated only at the end of the update.
This PR fixes this issue checking that even if ready, Kafka instance is not updating.