Skip to content

Commit

Permalink
Securing http link to https link (kubernetes-sigs#5617)
Browse files Browse the repository at this point in the history
Fix http link to https link for security

Signed-off-by: Nguyen Hai Truong <[email protected]>
  • Loading branch information
truongnh1992 authored Feb 13, 2020
1 parent 765d907 commit 516e9a4
Show file tree
Hide file tree
Showing 7 changed files with 9 additions and 9 deletions.
2 changes: 1 addition & 1 deletion RELEASE.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
4 changes: 2 additions & 2 deletions docs/ansible.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down Expand Up @@ -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/)
2 changes: 1 addition & 1 deletion docs/contiv.md
Original file line number Diff line number Diff line change
@@ -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

Expand Down
4 changes: 2 additions & 2 deletions docs/dns-stack.md
Original file line number Diff line number Diff line change
@@ -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).

Expand Down
2 changes: 1 addition & 1 deletion docs/integration.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
2 changes: 1 addition & 1 deletion docs/large-deployments.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
2 changes: 1 addition & 1 deletion docs/vars.md
Original file line number Diff line number Diff line change
Expand Up @@ -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:

Expand Down

0 comments on commit 516e9a4

Please sign in to comment.