openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 21:46:22 +01:00
Code Issues Releases Activity

OCPBUGS55735: OpenSSH key Setup

Browse Source
This commit is contained in:
Michael Burke
2025-05-30 08:57:40 -04:00
committed by openshift-cherrypick-robot
parent 1c428fe27d
commit 91ef412ce3
3 changed files with 30 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
modules/configuring-secret-for-wmco.adoc
View File

@@ -11,7 +11,11 @@ To run the Windows Machine Config Operator (WMCO), you must create a secret in t
.Prerequisites
* You installed the Windows Machine Config Operator (WMCO) using Operator Lifecycle Manager (OLM).
* You created a PEM-encoded file containing an RSA key.
* You created a PEM-encoded file containing a private key by using a strong algorithm, such as ECDSA.
+
--
include::snippets/wmco-key-ascii-encoding.adoc[]
--
.Procedure

8
modules/creating-the-vsphere-windows-vm-golden-image.adoc
View File

@@ -10,7 +10,13 @@ Create a vSphere Windows virtual machine (VM) golden image.
.Prerequisites
* You have created a private/public key pair, which is used to configure key-based authentication in the OpenSSH server. The private key must also be configured in the Windows Machine Config Operator (WMCO) namespace. This is required to allow the WMCO to communicate with the Windows VM. See the "Configuring a secret for the Windows Machine Config Operator" section for more details.
* You have created a private/public key pair, which is used to configure key-based authentication in the OpenSSH server. The private key must be configured in the Windows Machine Config Operator (WMCO) namespace so that the WMCO can communicate with the Windows VM.
+
--
include::snippets/wmco-key-ascii-encoding.adoc[]
--
+
See the "Configuring a secret for the Windows Machine Config Operator" section for more details.
[NOTE]
====

18
snippets/wmco-key-ascii-encoding.adoc Normal file
View File

@@ -0,0 +1,18 @@
// Text snippet included in the following modules:
//
// * modules/configuring-secret-for-wmco.adoc
// * modules/creating-the-vsphere-windows-vm-golden-image.adoc
:_mod-docs-content-type: SNIPPET
If you created the key pair on a {op-system-base-full} system, before you can use the public key on a Windows system, make sure the public key is saved using ASCII encoding. For example, the following PowerShell command copies a public key, encoding it for the ASCII character set:
[source,terminal]
----
C:\> echo "ssh-rsa <ssh_pub_key>" | Out-File <ssh_key_path> -Encoding ascii
----
where:
`<ssh_pub_key>`:: Specifies the SSH public key used to access the cluster.
`<ssh_key_path>`:: Specifies the path to the SSH public key.