summaryrefslogtreecommitdiffstats
path: root/roles/openshift_hosted/tasks/registry.yml
diff options
context:
space:
mode:
authorMichael Hanselmann <hansmi@vshn.ch>2017-09-28 14:12:20 +0200
committerMichael Hanselmann <hansmi@vshn.ch>2017-10-19 10:59:25 +0200
commit4abb7381bdf439dfc1ab371be231f856620d7e19 (patch)
tree90fce40cd0bd256e5293ee32ee630710cd08daca /roles/openshift_hosted/tasks/registry.yml
parent64f452f9081e380db41acf588a28fe4bb79a4e9e (diff)
downloadopenshift-4abb7381bdf439dfc1ab371be231f856620d7e19.tar.gz
openshift-4abb7381bdf439dfc1ab371be231f856620d7e19.tar.bz2
openshift-4abb7381bdf439dfc1ab371be231f856620d7e19.tar.xz
openshift-4abb7381bdf439dfc1ab371be231f856620d7e19.zip
Allow cluster IP for docker-registry service to be set
For historical reasons a small set of programs in our environments rely on the cluster-internal Docker registry having the IP address "172.30.1.1". So far we always had to patch in that address manually. Adding a variable on the "openshift_hosted" role allows the IP address to be set correctly when a cluster is installed.
Diffstat (limited to 'roles/openshift_hosted/tasks/registry.yml')
-rw-r--r--roles/openshift_hosted/tasks/registry.yml1
1 files changed, 1 insertions, 0 deletions
diff --git a/roles/openshift_hosted/tasks/registry.yml b/roles/openshift_hosted/tasks/registry.yml
index f1aa9c5a8..eaaac9da2 100644
--- a/roles/openshift_hosted/tasks/registry.yml
+++ b/roles/openshift_hosted/tasks/registry.yml
@@ -89,6 +89,7 @@
docker-registry: default
session_affinity: ClientIP
service_type: ClusterIP
+ clusterip: '{{ openshift_hosted_registry_clusterip | default(omit) }}'
- include: secure.yml
static: no