Description of problem: were following "F5 native integration" and have noticed that router default certificate is not being propagated to the F5. We were using --default-certs option while deploying the f5-router but it did not change anything. We still getting some default certificate which is set on F5 and is for "localhost.local" domain. If we manually replace this cert on F5, we can access OCP services over secured routes. Does f5-router pod configures default router certificate on F5? Are there prerequisites for this? Version-Release number of selected component (if applicable): 3.4 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
https://github.com/openshift/openshift-docs/pull/4090
Talked about this in standup and we are going to: - Clarify the command line args for F5 and haproxy in the docs (there's no current section) - In the CLI help we are going to add indications of which is for which router
CLI PR: https://github.com/openshift/origin/pull/13820
verified in atomic-openshift-3.6.86-1.git.0.3d5c716.el7.x86_64 and the cli help info has updated.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:1716