Create an informative issue (See each section, incomplete templates/issues won't be triaged)

Using the current documentation as a model, please complete the issue template. 

Note: Doc team updates the current version and the two previous versions (n-2). For earlier versions, we will address only high-priority, customer-reported issues for releases in support.

Prerequisite: Start with what we have

Always look at the current documentation to describe the change that is needed. Use the source or portal link for Step 4:

 - Use the Customer Portal: https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes

 - Use the GitHub link to find the staged docs in the repository: https://github.com/stolostron/rhacm-docs 

Describe the changes in the doc and link to your dev story

Provide info for the following steps:

1. - [X] Mandatory Add the required version to the Fix version/s field.

ACM 2.9.Z

2. - [ ] Mandatory Choose the type of documentation change.

      - [X] New topic in an existing section or new section

Add a new known issue in the App lifecycle known issue list

https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.9/html/release_notes/release-notes#known-issues-applications

1.3.4. Application known issues and limitations

1.3.4.20. Helm Chart with secret dependencies can't be deployed by ACM subscription 

Helm Chart allows user to define privacy data in a k8s secret and refer the secret in the value.yaml of the helm chart. 

e.g. In the following value.yaml, the username and password are actually given by the referred k8s secret resource dbsecret.

credentials:
  secretName: dbsecret
  usernameSecretKey: username
  passwordSecretKey: password

This is supported in helm binary CLI but not in the operator sdk helm lib.  Since ACM subscription controller applies the operator sdk helm lib to install/upgrade the helm chart, such helm chart with secret dependencies can't be deployed by ACM subscription.

Jira issue ref: https://issues.redhat.com/browse/ACM-8321?focusedId=23339654&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-23339654

      - [] Update to an existing topic

3. - [ ] Mandatory for GA content:
            
       - [ ] Add steps and/or other important conceptual information here: 
       
            
       - [ ] Add Required access level for the user to complete the task here:
       

       - [ ] Add verification at the end of the task, how does the user verify success (a command to run or a result to see?)
     
     
       - [ ] Add link to dev story here:

4. - [ ] Mandatory for bugs: What is the diff? Clearly define what the problem is, what the change is, and link to the current documentation: