diff --git a/RELEASE.md b/RELEASE.md
index da4dfa92e7180d9dcd3b04d346f46201a30c5f74..120e8ca6712fdfd848e60691b45602b6e7c1b095 100644
--- a/RELEASE.md
+++ b/RELEASE.md
@@ -29,7 +29,7 @@ The Kubespray Project is released on an as-needed basis. The process is as follo
   Older or newer versions are not supported and not tested for the given release.
 
 * There is no unstable releases and no APIs, thus Kubespray doesn't follow
-  [semver](http://semver.org/). Every version describes only a stable release.
+  [semver](https://semver.org/). Every version describes only a stable release.
   Breaking changes, if any introduced by changed defaults or non-contrib ansible roles'
   playbooks, shall be described in the release notes. Other breaking changes, if any in
   the contributed addons or bound versions of Kubernetes and other components, are
diff --git a/docs/ansible.md b/docs/ansible.md
index fc1555d4cdd47615492b497757a4c29fee901e38..00a9f3746ec8ed0416398b50385e8b82f039ec0c 100644
--- a/docs/ansible.md
+++ b/docs/ansible.md
@@ -68,7 +68,7 @@ Optional variables are located in the `inventory/sample/group_vars/all.yml`.
 Mandatory variables that are common for at least one role (or a node group) can be found in the
 `inventory/sample/group_vars/k8s-cluster.yml`.
 There are also role vars for docker, kubernetes preinstall and master roles.
-According to the [ansible docs](http://docs.ansible.com/ansible/playbooks_variables.html#variable-precedence-where-should-i-put-a-variable),
+According to the [ansible docs](https://docs.ansible.com/ansible/playbooks_variables.html#variable-precedence-where-should-i-put-a-variable),
 those cannot be overridden from the group vars. In order to override, one should use
 the `-e` runtime flags (most simple way) or other layers described in the docs.
 
@@ -181,4 +181,4 @@ bastion ansible_host=x.x.x.x
 ```
 
 For more information about Ansible and bastion hosts, read
-[Running Ansible Through an SSH Bastion Host](http://blog.scottlowe.org/2015/12/24/running-ansible-through-ssh-bastion-host/)
+[Running Ansible Through an SSH Bastion Host](https://blog.scottlowe.org/2015/12/24/running-ansible-through-ssh-bastion-host/)
diff --git a/docs/contiv.md b/docs/contiv.md
index 7fa334d1b9f8dc14a3d0ba2c8447738514c835fa..5281553f60b83338bf726d812fa4db0c58097278 100644
--- a/docs/contiv.md
+++ b/docs/contiv.md
@@ -1,6 +1,6 @@
 # Contiv
 
-Here is the [Contiv documentation](http://contiv.github.io/documents/).
+Here is the [Contiv documentation](https://contiv.github.io/documents/).
 
 ## Administrate Contiv
 
diff --git a/docs/dns-stack.md b/docs/dns-stack.md
index ccf0e0104c2ba53eb25f52877d19167b7bff3a85..ac40f68b40981129a652bc9e45e44f6ddb9ef296 100644
--- a/docs/dns-stack.md
+++ b/docs/dns-stack.md
@@ -1,7 +1,7 @@
 # K8s DNS stack by Kubespray
 
-For K8s cluster nodes, Kubespray configures a [Kubernetes DNS](http://kubernetes.io/docs/admin/dns/)
-[cluster add-on](http://releases.k8s.io/master/cluster/addons/README.md)
+For K8s cluster nodes, Kubespray configures a [Kubernetes DNS](https://kubernetes.io/docs/admin/dns/)
+[cluster add-on](https://releases.k8s.io/master/cluster/addons/README.md)
 to serve as an authoritative DNS server for a given ``dns_domain`` and its
 ``svc, default.svc`` default subdomains (a total of ``ndots: 5`` max levels).
 
diff --git a/docs/integration.md b/docs/integration.md
index 09908bf0108a36ccdaee445ea466c5268956c594..77ef03382fbf3416846e50c003b5afbd8a69568b 100644
--- a/docs/integration.md
+++ b/docs/integration.md
@@ -115,7 +115,7 @@ Branch name should be self explaining to you, adding date and/or index will help
      git cherry-pick <COMMIT_HASH>
      ```
 
-7. If your have several temporary-stage commits - squash them using [```git rebase -i```](http://eli.thegreenplace.net/2014/02/19/squashing-github-pull-requests-into-a-single-commit)
+7. If your have several temporary-stage commits - squash them using [```git rebase -i```](https://eli.thegreenplace.net/2014/02/19/squashing-github-pull-requests-into-a-single-commit)
 Also you could use interactive rebase (```git rebase -i HEAD~10```) to delete commits which you don't want to contribute into original repo.
 
 8. When your changes is in place, you need to check upstream repo one more time because it could be changed during your work.
diff --git a/docs/large-deployments.md b/docs/large-deployments.md
index 072c2bc75d4224132e3d041a3929023c0bc09278..1aa59e101c34529b00cff652d888917731dde8ad 100644
--- a/docs/large-deployments.md
+++ b/docs/large-deployments.md
@@ -3,7 +3,7 @@ Large deployments of K8s
 
 For a large scaled deployments, consider the following configuration changes:
 
-* Tune [ansible settings](http://docs.ansible.com/ansible/intro_configuration.html)
+* Tune [ansible settings](https://docs.ansible.com/ansible/intro_configuration.html)
   for `forks` and `timeout` vars to fit large numbers of nodes being deployed.
 
 * Override containers' `foo_image_repo` vars to point to intranet registry.
diff --git a/docs/vars.md b/docs/vars.md
index 91cfb83d8bdfce7abc254c203fb293f1bf530d31..d2b3ef6006fe8b026e8511e1263ad161bf161e7e 100644
--- a/docs/vars.md
+++ b/docs/vars.md
@@ -3,7 +3,7 @@
 ## Generic Ansible variables
 
 You can view facts gathered by Ansible automatically
-[here](http://docs.ansible.com/ansible/playbooks_variables.html#information-discovered-from-systems-facts).
+[here](https://docs.ansible.com/ansible/playbooks_variables.html#information-discovered-from-systems-facts).
 
 Some variables of note include: