In the dev-preview we discovered that when we configure multiple resources of the same kind in the resource ManagedClusterAddOn, that then only one of those resources will be added to the status of ManagedClusterAddOn and inherently be tracked by the addon-framework to triggers reconciliations. This is a big shortcoming that we avoided by reconciling the Spec of the ManagedClusterAddOn in the parts of the project where we knew that multiple instances of the same resource could be configured.

Acceptance Criteria

1. Users will be able to configure multiple resources of the same kind in the resource ManagedClusterAddOn
2. By reconciling the ManagedClusterAddOn Status the addon will have access to all the resources configured by the user