Bug 1465068 - Router wildcard certificates at installation time
Summary: Router wildcard certificates at installation time
Keywords:
Status: CLOSED EOL
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 3.5.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Vikram Goyal
QA Contact: Vikram Goyal
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-26 14:34 UTC by Eduardo Minguez
Modified: 2019-08-10 06:40 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-10 06:40:20 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Eduardo Minguez 2017-06-26 14:34:01 UTC
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 14:45:30 UTC
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.