From 62b95f5f2807a8ea372ecadaf78ec8a84a4b33f7 Mon Sep 17 00:00:00 2001 From: amolvkharche <83961171+amolvkharche@users.noreply.github.com> Date: Thu, 16 Feb 2023 12:47:40 +0530 Subject: [PATCH 1/3] Update faq.md --- docs/faq.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/faq.md b/docs/faq.md index f5e5b85fb3f..c08cab60d43 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -48,3 +48,9 @@ New password for default administrator (user-xxxxx): ### I added an additional disk with partitions. Why is it not getting detected? As of Harvester v1.0.2, we no longer support adding additional partitioned disks, so be sure to delete all partitions first (e.g., using `fdisk`). + +### How to add ssh key to the Harvester nodes using a modified config file ? + +You can modify /oem/99_custom.yaml (or 90_custom.yaml) to add authorized keys after login harvester through ssh. +After modification, you can reboot the node to see the difference. +Please refer https://rancher.github.io/elemental-toolkit/docs/reference/cloud_init/#stagesstage_idstep_nameauthorized_keys . From c6c73cd3a1c47336db762a92e278e024660ea1a4 Mon Sep 17 00:00:00 2001 From: amolvkharche <83961171+amolvkharche@users.noreply.github.com> Date: Tue, 21 Feb 2023 11:10:25 +0530 Subject: [PATCH 2/3] Update faq.md --- docs/faq.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/faq.md b/docs/faq.md index c08cab60d43..a3e4f02d5ef 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -51,6 +51,10 @@ As of Harvester v1.0.2, we no longer support adding additional partitioned disks ### How to add ssh key to the Harvester nodes using a modified config file ? +Option 1. Non Persistent (Temporary) +If the user just wants it to work in the runtime without rebooting then please add keys to /home/rancher/.ssh/authorized_keys and that can change the runtime setting (but it's not persistent between reboots). + +Option 2. Persistent You can modify /oem/99_custom.yaml (or 90_custom.yaml) to add authorized keys after login harvester through ssh. After modification, you can reboot the node to see the difference. Please refer https://rancher.github.io/elemental-toolkit/docs/reference/cloud_init/#stagesstage_idstep_nameauthorized_keys . From a9812fef444cd54219b5ac4d8992dac7e6699640 Mon Sep 17 00:00:00 2001 From: Guangbo Date: Wed, 16 Aug 2023 09:07:40 +0800 Subject: [PATCH 3/3] Apply suggestions from code review Co-authored-by: Lucas Saintarbor --- docs/faq.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/faq.md b/docs/faq.md index a3e4f02d5ef..88f93edcc4a 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -47,14 +47,14 @@ New password for default administrator (user-xxxxx): ### I added an additional disk with partitions. Why is it not getting detected? -As of Harvester v1.0.2, we no longer support adding additional partitioned disks, so be sure to delete all partitions first (e.g., using `fdisk`). +As of Harvester v1.0.2, adding additional partitioned disks is no longer supported, be sure to delete all partitions first (e.g., using `fdisk`). -### How to add ssh key to the Harvester nodes using a modified config file ? +### How to add ssh authorized keys to a Harvester node using a modified config file? Option 1. Non Persistent (Temporary) -If the user just wants it to work in the runtime without rebooting then please add keys to /home/rancher/.ssh/authorized_keys and that can change the runtime setting (but it's not persistent between reboots). +To dynamically add users in the runtime without rebooting, add ssh authorized keys to /home/rancher/.ssh/authorized_keys. These changes are not persistent between reboots. Option 2. Persistent -You can modify /oem/99_custom.yaml (or 90_custom.yaml) to add authorized keys after login harvester through ssh. -After modification, you can reboot the node to see the difference. -Please refer https://rancher.github.io/elemental-toolkit/docs/reference/cloud_init/#stagesstage_idstep_nameauthorized_keys . +After you ssh login to Harvester, add ssh authorized keys to your /oem/99_custom.yaml or 90_custom.yaml. These changes are persistent between reboots. +After you modify your cloud-init script, reboot the node to see the changes take effect. +See [Cloud-init support - stages.STAGE_ID.STEP_NAME.authorized_keys](https://rancher.github.io/elemental-toolkit/docs/reference/cloud_init/#stagesstage_idstep_nameauthorized_keys) for details on adding ssh authorized keys to a config file.