Support ssh-key-dir on OKD/FCOS#2688
Conversation
|
Skipping CI for Draft Pull Request. |
|
/test e2e-aws |
|
/test e2e-aws |
|
/test e2e-aws |
|
@LorbusChris, #2087 will need to be reverted for this to work correct? |
|
@fortinj66 yes. The plan is to manage the |
1bdb52a to
2f91cc6
Compare
|
/retest-required |
|
/test e2e-aws |
|
The order in which we will merge things here will matter unfortunately as this involves Ignition package changes too. One option we have is to make sure we coordinate this to happen on a specific day. |
travier
left a comment
There was a problem hiding this comment.
Code LGTM but I'm not really familiar with the MCO code base.
|
/test e2e-agnostic-upgrade |
|
/test e2e-aws |
|
/test e2e-aws |
875ded7 to
40394f8
Compare
3f433ca to
1fd1e6e
Compare
|
I've removed the RHCOS9 parts from this PR |
ssh-key-dir on FCOS and future RHCOS9ssh-key-dir on OKD/FCOS
1fd1e6e to
efb7685
Compare
In older versions of OKD, the SSH keys were written to `/home/core/.ssh/authorized_keys`. Newer versions of OKD will expect the keys at `/home/core/.ssh/authorized_keys.d/ignition`. In the case of a newer version of OKD, the keys file is removed from the legacy path in the updateSSHKeys function. It will then be recreated at the new fragment path by the atomicallyWriteSSHKey function that is called right after.
Usage of ssh-key-dir is now supported on FCOS (OKD)
efb7685 to
05142f3
Compare
sinnykumari
left a comment
There was a problem hiding this comment.
Thanks Christain for making the changes.
/lgtm
|
Just noticed #2688 (comment) , @LorbusChris do we need any ignition update here? Putting hold until this question is addressed. |
No, this will only be needed for RHCOS9 |
|
/hold cancel |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: LorbusChris, sinnykumari, travier The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
3 similar comments
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
@LorbusChris: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
3 similar comments
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
- What I did
In older versions of OKD, the SSH keys were written to
/home/core/.ssh/authorized_keys. Newer versions of OKD willexpect the keys at
/home/core/.ssh/authorized_keys.d/ignition.In the case of a newer version of OKD, the keys file is removed
from the legacy path in the updateSSHKeys function.
It will then be recreated at the new fragment path by the
atomicallyWriteSSHKey function that is called right after.
- How to verify it
CI
- Description for the changelog
Support ssh-key-dir on OKD/FCOS