Bug 1838998

Summary: Service Mesh automatic route creation doesn't allow routes with edge termination
Product: OpenShift Container Platform Reporter: Felipe M <fmarting>
Component: DocumentationAssignee: Claire Bremble <cbremble>
Status: CLOSED DEFERRED QA Contact: Xiaoli Tian <xtian>
Severity: low Docs Contact: Claire Bremble <cbremble>
Priority: unspecified    
Version: 4.4CC: cbremble, lmurthy
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-02-07 20:32:46 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Felipe M 2020-05-22 10:02:36 UTC 
Document URL: 
https://docs.openshift.com/container-platform/4.4/service_mesh/service_mesh_day_two/ossm-auto-route.html

Section Number and Name:
N/A

Describe the issue: 
Following the documentation of the Service Mesh Automatic Route Creation it does not specify how routes are created in regarding to it's TLS termination.

Generating a Route with the provided guide creates a route and gateway without TLS, so if the customer requires edge termination the route must be modified manually.

It seems that the IOR in charge of this behaviour has no support for edge routes, it only creates either non-tls or passthrough routes, depending on the gateway resource created. [1]

Suggestions for improvement: 
- Documentation should specify this kind of route limitation and explain that for edge routes it has to be created manually.
- If I missed something and there's a way to automatically create edge routes it should be documented as well.

Additional information: 
Bug is opened for 4.4 but affect past versions as well.

[1] https://github.com/Maistra/ior/blob/67fd95659451a003898cb42ebe79acd4d1c56a17/pkg/route/route.go#L164
Comment 1 Vidya 2021-02-08 09:54:55 UTC 
The documentation effort for this bz will be tracked in https://issues.redhat.com/browse/OSSMDOC-239
Comment 12 Claire Bremble 2023-02-07 20:33:37 UTC 
Progress on this bug can be followed here: https://issues.redhat.com/browse/OSSM-3213