Value Statement

• If the add-on agent running on the managed cluster needs to access any service other than the hub kube-apiserver, a small enhancement is required for the add-on to support proxy connection between hub and managed cluster;
• If the add-on agent running on the managed cluster needs to access outside service/resource (not on the hub cluster), a small enhancement is required for the add-on to support proxy config in AddOnDeploymentConfig API;
• If the underlying transport does not support HTTP/HTTPS proxy, please document this limitation.

Please follow this guide (https://issues.redhat.com/browse/ACM-6569?focusedId=22769927&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-22769927) for the details of the enhancement.

And you can find the whole proposal here: https://docs.google.com/document/d/1QKK-sQ_KNuYdFily2G_cIuoyVdy6hUODmuRuA6vBArE/edit?usp=sharing

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

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

Secure Design

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

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the [Customer
  Portal_doc_issue template](
  https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
  and ensure doc acceptance criteria is met. Link the development issue to
  the doc issue.
• [ ] Provide input to the QE team, and ensure QE acceptance criteria
  (established between story owner and QE focal) are met.

Support Readiness

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