public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-25 04:28:15 +00:00
Code Issues Packages Projects Releases Wiki Activity

Using SSH certificates in RKE

Browse Source
This commit is contained in:
Sebastiaan van Steenis
2019-03-22 10:25:30 -07:00
committed by Denise Schannon
parent 6302779512
commit 778674fa2d
2 changed files with 34 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rke/v0.1.x/en/config-options/bastion-host/_index.md
+13
View File
@@ -16,6 +16,11 @@ bastion_host:
# -----BEGIN RSA PRIVATE KEY-----
#
# -----END RSA PRIVATE KEY-----
# Optionally using SSH certificates
# ssh_cert_path: /home/user/.ssh/id_rsa-cert.pub
# or
# ssh_cert: |-
# ssh-rsa-cert-v01@openssh.com AAAAHHNza...
```
## Bastion Host Options
@@ -39,3 +44,11 @@ You specify the path, i.e. `ssh_key_path`, for the SSH private key to be used wh
### SSH Key
Instead of setting the path to the SSH key, you can specify the actual key, i.e. `ssh_key`, to be used to connect to the bastion host.
### SSH Certificate Path
You specify the path, i.e. `ssh_cert_path`, for the signed SSH certificate to be used when connecting to the bastion host.
### SSH Certificate
Instead of setting the path to the signed SSH certificate, you can specify the actual certificate, i.e. `ssh_cert`, to be used to connect to the bastion host.
content/rke/v0.1.x/en/config-options/nodes/_index.md
+21
View File
@@ -23,6 +23,19 @@ nodes:
-----BEGIN RSA PRIVATE KEY-----
-----END RSA PRIVATE KEY-----
- address: 3.3.3.3
user: ubuntu
role:
- worker
ssh_key_path: /home/user/.ssh/id_rsa
ssh_cert_path: /home/user/.ssh/id_rsa-cert.pub
- address: 4.4.4.4
user: ubuntu
role:
- worker
ssh_key_path: /home/user/.ssh/id_rsa
ssh_cert: |-
ssh-rsa-cert-v01@openssh.com AAAAHHNza...
- address: example.com
user: ubuntu
role:
@@ -69,6 +82,14 @@ For each node, you specify the path, i.e. `ssh_key_path`, for the SSH private ke
Instead of setting the path to the SSH key, you can alternatively specify the actual key, i.e. `ssh_key`, to be used to connect to the node.
### SSH Certificate Path
For each node, you can specify the path, i.e. `ssh_cert_path`, for the signed SSH certificate to be used when connecting to this node.
### SSH Certificate
Instead of setting the path to the signed SSH certificate, you can alternatively specify the actual certificate, i.e. `ssh_cert`, to be used to connect to the node.
### Kubernetes Roles
You can specify the list of roles that you want the node to be as part of the Kubernetes cluster. Three roles are supported: `controlplane`, `etcd` and `worker`. Node roles are not mutually exclusive. It's possible to assign any combination of roles to any node. It's also possible to change a node's role using the upgrade process.