link titleh4. Description of problem:

The addon status is blocked in a progressing state with an error message "progressing... mca and work configs mismatch" when we set a default config for the addondeploymentconfigs resource in the ClusterManagementAddOn resource.

This appears following the upgrade of the addon-framework.

The spec hash is not updated in the status of the ClusterManagementAddOn resource, leading to this blocked state.

For it to be managed automatically by the addon-framework, we would need to run our controller with it. But this would probably require a heavy and risky refactoring.
Another solution would be to implement this spec hash update in our own code.

Slack: https://redhat-internal.slack.com/archives/CUU609ZQC/p1756374111681389

We might also add the label back like in this PR as we are not using the addon-framework manager...