Story (Required)

Background/Approach (Required)

See parent epic for details.

HOWEVER, there are significant open questions on how this should work:

• On initial read, to me, what is being described sounds more like edge TLS termination, rather than re-encrypt
• If we ARE using re-encrypt, where do we get the certificate from?
• When this item was last discussed, it sounded like Jann had some significant requirements for this, which we should extract from him and consider.

The owner of this story should build a familiarity with the various OpenShift Routes settings, and work with stakeholders (Harriet, Jann, Abhishek, myself, anyone else interested) to ensure that we all agree on what needs to be implemented.

Resources

Route Configuration in OpenShift: https://docs.openshift.com/container-platform/4.15/networking/routes/route-configuration.html
Creating a re-encrypt route with a custom certificate: https://docs.openshift.com/container-platform/4.15/networking/routes/secured-routes.html

Acceptance Criteria (Mandatory)

• Work with stakeholders (see above) to gather requirements for this epic, and build consensus
  • Based on earlier discussions around the epic description, it sounds like folks are less clear (there is less consensus) on the details than it may seem.
• Prepare a design document which proposes a solution and present to the team
  • Document should describe new behaviour
  • How to handle any breaking changes
• Get sign off from stakeholders, and open new story with details