Description of problem:

When you configure a ClusterInstance with a proxy, the proxyConfig is not propagated to the KlusterletAddonConfig:
https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.14/html/add-ons/acm-managed-adv-config#enable[...]-addon

it could happen that there exists a proxy between management and managed clusters. When you configure the ClusterInstance, you fill all the config about KlusterletAddonConfig, and you expect this is propagated to all the needed CR. If we dont propagate it to the KlustereletAddonConfig, we could miss some communications between the spokes and the hub.

Version-Release number of selected component (if applicable):

ACM2.13

How reproducible:

An environment where there is a proxy between Management and ManagedClusters. Create a ClusterInstance with the Proxy Info. The cluster is created, because most of the CR/Configurations propagate that info. But KlusterletAddonConfig no. I see this, for example, on a failing Multicluster Observability Addon.

Steps to Reproduce:

1.  
2.  
3. ...

Actual results:

Expected results:

Additional info: