3. What is the nature and description of the request?

A volume that doesn't fail if it's secret doesn't exist. E.g:
volumes:
        - name: deploy-secrets
          secret:
            secretName: deploy-secrets
volumeMounts:
          - mountPath: /deploysecrets
            name: deploy-secrets
            readOnly: true

If I have this in a DeployConfig in a template, and try to create it when the deploy-secrets Secret does not exist, it will fail and say the Secret must exist

4. Why does the customer need this? (List the business requirements here)  
We use secrets to provide additional features. If secrets could be optional and decided on create time, then these features could be optional.
      
5. How would the customer like to achieve this? (List the functional requirements here)
Add a label to the volume called "optional".
If the label exists, and the secret does not exist when the volume is created, it does not fail
      
6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.  
Define a secret volume with the "optional" label in a deployment config, create the deployment config when the secret doesn't exist

7. Is there already an existing RFE upstream or in Red Hat Bugzilla?  

8. Does the customer have any specific timeline dependencies and which release would they like to target?
 
9. Is the sales team involved in this request and do they have any additional input? 
      
10. List any affected packages or components.  
      
11. Would the customer be able to assist in testing this functionality if implemented?  
yes