summaryrefslogtreecommitdiffstats
path: root/roles/openshift_manage_node
diff options
context:
space:
mode:
authorNick Bartos <flamingo@2thebatcave.com>2017-12-05 15:02:52 +1100
committerNick Bartos <flamingo@2thebatcave.com>2018-01-08 07:44:35 +1100
commit6daf71565fd69e9ddb2ac20e787d49f74cf7a9d7 (patch)
tree217ed334a99474d8307a65c75a4c864acbabf7d8 /roles/openshift_manage_node
parenta5eee09d02120bb16d7f81d1b05982e1a69df4dc (diff)
downloadopenshift-6daf71565fd69e9ddb2ac20e787d49f74cf7a9d7.tar.gz
openshift-6daf71565fd69e9ddb2ac20e787d49f74cf7a9d7.tar.bz2
openshift-6daf71565fd69e9ddb2ac20e787d49f74cf7a9d7.tar.xz
openshift-6daf71565fd69e9ddb2ac20e787d49f74cf7a9d7.zip
Contiv multi-master and other fixes
Contiv's etcd was not being deployed correctly when using more than one master. To make it easier to manage, it has been moved into a k8s container. The api proxy was hardcoded to an old version (1.1.1), and in some environments would run into a docker error. This has been moved into a k8s container for easier management. The firewall was too permissive on several ports. Many were open to the world when they should have only been accessible inside the cluster. Many of the contiv role variables were not prefixed with 'contiv', which may end up clobbering variables from another role. Now all the contiv specific role variables start with 'contiv_'. The api proxy's default self-signed certificate was bundled with the role. This means someone with read-only MITM access and this key could decrypt traffic. Granted a user defined certificate from a trusted CA should be used in a production environment, it is still better to generate one in each environment when one is not provided.
Diffstat (limited to 'roles/openshift_manage_node')
0 files changed, 0 insertions, 0 deletions