Bug 1428025 - [3.5] Router default cert is not being propagated to the F5
Summary: [3.5] Router default cert is not being propagated to the F5
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 3.5.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Vikram Goyal
QA Contact: Vikram Goyal
Vikram Goyal
URL:
Whiteboard:
Depends On: 1427774
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-01 17:45 UTC by Eric Paris
Modified: 2020-12-14 08:16 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
Cause: Vservers are not created automatically by f5 router pod. Consequence: Default certs are not copied by the pod either, hence. Workaround (if any): Docs have been updated on how to manually create vservers. Result: Not​ a blocker to workflow. When automatic creation of vservers is done by pod, we will not need the manual workaround.
Clone Of: 1427774
Environment:
Last Closed: 2018-05-09 00:10:45 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Comment 1 Rajat Chopra 2017-04-10 22:42:38 UTC 
The documentation has been fixed on how to provide the default certificate as part of the setup. Automatically creating the virtual servers is a larger feature that will be planned for later.
Doc fix PR: https://github.com/openshift/openshift-docs/pull/4090
Comment 2 Hongan Li 2017-04-11 03:21:05 UTC 
it is same doc PR and has been verified in https://bugzilla.redhat.com/show_bug.cgi?id=1431660
Note You need to log in before you can comment on or make changes to this bug.