Goal
As a RHOSO user, I want to secure my web client communication with a load balancer using using two-way TLS authentication.

Acceptance Criteria

• Acceptance Criteria articulates and defines the value proposition - what is required to meet the goal and intent of this Epic 
• The Acceptance Criteria provides a detailed definition of scope and the expected outcomes - from a users point of view

Open questions

1. Is this feature fully supported or technical preview?
   Full support: Documentation will be published on the Customer Portal
2. Does the procedural content need to be tested by QE?
   Yes: QE needs to create a doc testing ticket per How-to Jira with the docs team.
3. Does the doc epic need a release note in addition to the parent feature?
   No: The engineering feature or epic might still need a release note. Engineers need to follow the guidance set in How-to Jira with the docs team.
4. Are there any upstream or internal resources that the writer can use for planning and drafting the content?
   Unclear.
5. Does the content require input from multiple DFGs?
   No: Stories are not required unless the epic needs to be divided to user stories that can be delivered separately (for personal use, consider sub-tasks instead)
6. What type of information does the user need to know in order to use the feature?
   1. Procedures to implement or enable the feature
      To be determined.
   2. Procedures to customize or configure the feature after installation
      To be determined.
   3. Procedures or considerations for upgrades, adoption, or minor updates
      To be determined.
   4. Procedures to verify that the feature is enabled and is working as expected
      To be determined.
   5. Procedures to operate or maintain the feature
      To be determined.
   6. Concepts that need to be explained or planning decisions that must be made before the user can perform any of these procedures
      To be determined.
   7. Permissions level required (RHOSO/OCP) or security considerations
      To be determined.
   8. Known issues, limitations, or troubleshooting guidance
      To be determined.
7. Does the content need to be included in any of the following guides?
   1. Validated architecture (VA) guide: Is the content a part of a VA workflow, such as HCI, NFV, BGP, etc?
      NO
   2. Planning guide: Are there prerequisites or planning decisions to add to the Planning guide?
      NO
   3. Deployment/Customization guide: Does the feature need to be enabled during the deployment process, or can it be enabled post-deployment?
      Post-deployment
   4. Adoption/minor updates guide: Are there any considerations or impact of this feature on adoption from pre-18 environments or from earlier 18z versions?
      NO