Skip to content
Snippets Groups Projects
Commit 3e007df9 authored by Alexander Block's avatar Alexander Block
Browse files

Add documentation about bastion hosts

parent 06584ee3
No related branches found
No related tags found
No related merge requests found
...@@ -119,3 +119,17 @@ ansible-playbook -i inventory/inventory.ini cluster.yaml \ ...@@ -119,3 +119,17 @@ ansible-playbook -i inventory/inventory.ini cluster.yaml \
``` ```
Note: use `--tags` and `--skip-tags` wise and only if you're 100% sure what you're doing. Note: use `--tags` and `--skip-tags` wise and only if you're 100% sure what you're doing.
Bastion host
--------------
If you prefer to not make your nodes publicly accessible (nodes with private IPs only),
you can use a so called *bastion* host to connect to your nodes. To specify and use a bastion,
simply add a line to your inventory, where you have to replace x.x.x.x with the public IP of the
bastion host.
```
bastion ansible_ssh_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/)
\ No newline at end of file
...@@ -8,7 +8,7 @@ ...@@ -8,7 +8,7 @@
# node6 ansible_ssh_host=95.54.0.17 # ip=10.3.0.6 # node6 ansible_ssh_host=95.54.0.17 # ip=10.3.0.6
# ## configure a bastion host if your nodes are not publicly reachable # ## configure a bastion host if your nodes are not publicly reachable
# bastion ansible_ssh_host=xxx.xxx.xxx.xxx # bastion ansible_ssh_host=x.x.x.x
# [kube-master] # [kube-master]
# node1 # node1
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment