Update all configs to current upstream state.
Add more resources (unable to pass tests now)...

Enable swap

ingress-nginx: Upgrade to 0.17.1

Upstream Changes:

-   ingress-nginx 0.17.1 (https://github.com/kubernetes/ingress-nginx/releases/tag/nginx-0.17.1)
-   Remove duplicated `securityContext` (https://github.com/kubernetes/ingress-nginx/pull/2705)
-   Remove --publish-service flag, in favor of DaemonSet + hostPort

Close #2998
Close #2999

cert-manager: Upgrade to 0.4.0

allow for setting the cacert on openstack cloud provider

Adding cluster_name to api cert alt name for vault

Configure openstack subnet cidr

dashboard_token_ttl option override possibility with default

Variablize kube_proxy_healthz_bind_address

update .gitignore

Add support for docker 17.09

Fix a broken symbolic link for group_vars

availability zones support for OpenStack

Service file binary place mismatch

Upstream Changes:

-   cert-manager 0.4.0 (https://github.com/jetstack/cert-manager/releases/tag/v0.4.0)

According to cluster/binary.yml vault binary will be placed to `{{ bin_dir }}` and according to `inventory/sample/group_vars/all.yml` that is 
`inventory/sample/group_vars/all.yml`

Fix yaml roles error

fix missing libraries on newer coreos versions

- add vim default backup file *~
- remove duplicated *sw[pon]

Clarify etcd deployment script failure mechanism

set LC_ALL=C for growpart

allow masters, nodes and gluster nodes (within each group) to be scheduled
on differents AZ.

add openstack security group for traffic to 30000-32767/tcp on worker nodes

Follow upstream

Attempting to clarify the language surrounding the etcd node deployment script failure mechanism. I had this error when doing a new cluster deployment last night and, though it should have been, it wasn't immediately apparent to me what was causing the issue (since my default master node hostnames do not specify whether they are also acting as etcd replicas).

Fix label of registry in README

This will make NodePort services work out of the box

Remove double slash

Even without this PR, the operation works well.
However, it is better to use a single slash rather than
a double slash in the path.

This fixes #3014