summaryrefslogtreecommitdiffstats
path: root/playbooks/aws/openshift-cluster/vars.yml
diff options
context:
space:
mode:
authorDavid Moreau-Simard <dms@redhat.com>2017-05-19 14:28:42 -0400
committerDavid Moreau-Simard <dms@redhat.com>2017-07-23 10:13:03 -0400
commitd7d97964f5e3b5d2df9985e7f9d7b74a974458cb (patch)
tree6295ba96709b55bdef549ab4011422930076e0ae /playbooks/aws/openshift-cluster/vars.yml
parent2a706ad80a4286afc4fe5a1cc0cadab302bc7291 (diff)
downloadopenshift-d7d97964f5e3b5d2df9985e7f9d7b74a974458cb.tar.gz
openshift-d7d97964f5e3b5d2df9985e7f9d7b74a974458cb.tar.bz2
openshift-d7d97964f5e3b5d2df9985e7f9d7b74a974458cb.tar.xz
openshift-d7d97964f5e3b5d2df9985e7f9d7b74a974458cb.zip
Refactor openshift_hosted's docker-registry route setup
We have identified an issue where a docker-registry service set up as 'reencrypt' with a provided certificate and a self-signed certificate on the pod does not authorize users to push images. If the docker-registry service is set up as 'passthrough' with the same provided certificate, everything works. In light of this, this commit essentially adds support for configuring provided certificates with a passthrough route while maintaining backwards compatibility with the other use cases. The default remains 'passthrough' with self-generated certificates. Other miscellaneous changes include: - Move fact setup that were only used in secure.yml there - Omit the hostname for the route if there are none to configure, oc_route takes care of handling the default - Replace hardcoded /etc/origin/master by openshift_master_config_dir
Diffstat (limited to 'playbooks/aws/openshift-cluster/vars.yml')
0 files changed, 0 insertions, 0 deletions