Bug 1465068 - Router wildcard certificates at installation time
Router wildcard certificates at installation time
Status: NEW
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation (Show other bugs)
3.5.0
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Vikram Goyal
Vikram Goyal
Vikram Goyal
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-06-26 10:34 EDT by Eduardo Minguez
Modified: 2017-06-26 10:45 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Eduardo Minguez 2017-06-26 10:34:01 EDT
Document URL: https://docs.openshift.com/container-platform/3.5/install_config/router/default_haproxy_router.html#using-wildcard-certificates

Section Number and Name: using wildcard certificates

Describe the issue: Instructions are provided for a cluster up & running, but they are missing on how to do it at installation time.

Suggestions for improvement: Add the proper ansible variables values (in case they exist) for customizing the wildcard certificate at installation time.

Additional information:
Comment 1 Eduardo Minguez 2017-06-26 10:45:30 EDT
Actually, it looks like there are some ansible variables that can be used for this https://github.com/openshift/openshift-ansible/blob/master/roles/openshift_hosted/README.md (openshift_hosted_router_certificate)

Note You need to log in before you can comment on or make changes to this bug.