Value Statement

Currently users can specify the proxy configuration in addonDeploymentConfig

apiVersion: addon.open-cluster-management.io/v1alpha1
kind: AddOnDeploymentConfig
metadata:
  name: addon-proxy-settings
  namespace: cluster1
spec:
  proxyConfig:
    httpProxy: "http://10.0.109.153:3128"
    httpsProxy: "https://10.0.109.153:3129"
    noProxy: ".cluster.local,.svc,10.96.0.1"

But the proxyConfig won't be automatically propagated into the associated the addonTemplate. 

That would be idea if this case can be supported so that users can set up the proxy config in one AddonDeploymentConfig, link it to a clusterManagementAddon with the addonTemplate. The addon deployed on all managed clusters will have the proxy configuration settled automatically

Definition of Done for Engineering Story Owner (Checklist)

• ...

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [x] Unit/function tests have been automated and incorporated into the
  build.
• [x] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [x] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [x] Create an informative documentation issue using the Customer

Portal Doc template that you can access from [The Playbook](

https://docs.google.com/document/d/1YTqpZRH54Bnn4WJ2nZmjaCoiRtqmrc2w6DdQxe_yLZ8/edit#heading=h.9fvyr2rdriby),

and ensure doc acceptance criteria is met.

• Call out this sentence as it's own action:

• [x] Link the development issue to the doc issue.

Support Readiness

• [x] The must-gather script has been updated.