Update code-of-conduct.md

Refer to kubernetes/community as authoritative source for code of conduct

This does not update v1.9.0, but fixes two incompatibilities
when trying to deploy v1.9.0.

Starting with Kubernetes v1.8.4, kubelet ignores the AWS cloud
provider string and uses the override hostname, which fails
Node admission checks.

Fixes #2094

Renaming runtime docker_version to prevent setting that
value on the command line from breaking the play run.

This fixes #2081

Add possibility to create default OpenStack Cinder Storage Class

Closes: #1609

Ansible cannot seem to handle omitting delegate_to since v2.4.0.0.

Possibly related: https://github.com/ansible/ansible/issues/30760

Fixing alt_names for vault cert generation

set docker_version fact regardless of docker_dns in use

Fix domain id for OpenStack provider

Change OpenStack inventory to python2

Added proxy_env to scale and upgrade playbooks

Adding retries for vault-temp to come online

OpenStack authentication does not support using a mix of DomainID and
DomainName, only one or the other should be used.

append newline char to vault generated certs

For distribution who ship python3 as default python, it breaks the
inventory script as it is not compatible with python3.

- adding additional directories to cleanup (rkt/vault)
- targeting kubespray ansible groups instead of all

Update main.yml

Delete helm home

Remove RBAC from boolean checks

Add minimal keepalived-cloud-provider support

* Remove the network device created by the flannel

Remove the network device created by the flannel

* Modify flannel.1 device path

Modify flannel.1 device path

* remove trailing spaces

* Adding changes to handle updation of yum cache in rhel.

* Removed the redundant spaces

Kubernetes Dashboard v1.7.1 Refactor

Change altnames to alt_names

* Adding bastion and private network provisioning for openstack terraform

* Remove usage of floating-ip property

* Combine openstack instances + floating ips

* Fix relating floating IPs to hosts for openstack builds

* Tighten up security groups

Allow ssh into all instances with floating IP

* Add the gluster hosts to the no-floating group

* Break terraform into modules

* Update README and var descriptions to match current config

* Remove volume property in gluster compute def

* Include cluster name in internal network and router names

* Make dns_nameservers a variable

* Update k8s version to 1.8.4

* Update main.yml

* Properly tag instances and subnets with `kubernetes.io/cluster/$cluster_name`

This is required by kubernetes to support multiple clusters in a single vpc/az

* Get rid of loadbalancer_apiserver_address as it is no longer needed

* Dynamically retrieve aws_bastion_ami latest reference by querying AWS rather than hard coded

* Dynamically retrieve the list of availability_zones instead of needing to have them hard coded

* Limit availability zones to first 2, using slice extrapolation function

* Replace the need for hardcoded variable "aws_cluster_ami" by the data provided by Terraform

* Move ami choosing to vars, so people don't need to edit create infrastructure if they want another vendor image (as suggested by @atoms)

* Make name of the data block agnostic of distribution, given there are more than one distribution supported

* Add documentation about other distros being supported and what to change in which location to make these changes

* Allow setting --bind-address for apiserver hyperkube

This is required if you wish to configure a loadbalancer (e.g haproxy)
running on the master nodes without choosing a different port for the
vip from that used by the API - in this case you need the API to bind to
a specific interface, then haproxy can bind the same port on the VIP:

root@overcloud-controller-0 ~]# netstat -taupen | grep 6443
tcp        0      0 192.168.24.6:6443       0.0.0.0:*               LISTEN      0          680613     134504/haproxy
tcp        0      0 192.168.24.16:6443      0.0.0.0:*               LISTEN      0          653329     131423/hyperkube
tcp        0      0 192.168.24.16:6443      192.168.24.16:58404     ESTABLISHED 0          652991     131423/hyperkube
tcp        0      0 192.168.24.16:58404     192.168.24.16:6443      ESTABLISHED 0          652986     131423/hyperkube

This can be achieved e.g via:

kube_apiserver_bind_address: 192.168.24.16

* Address code review feedback

* Update kube-apiserver.manifest.j2