-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added question how to add ssh key in faq.md #285
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for harvester-preview ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
@amolvkharche Thanks for the doc. It would be nice to also mention that updating |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Made some style changes
- Made changes to sentence structure
- Should the docs page (https://docs.harvesterhci.io/v1.1/vm/access-to-the-vm/#ssh-access) be referenced?
@guangbochen Is this PR still valid? |
Co-authored-by: Lucas Saintarbor <lucas.saintarbor@suse.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a nit, others LGTM.
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 | ||
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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought in the harvester cluster, we only have /oem/90_custom.yaml
.
Maybe we could remove the /oem/99_custom.yaml
?
No description provided.