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

WMCO add link for SSH key prerequisites

Browse Source
This commit is contained in:
Michael Burke
2025-11-03 08:26:31 -05:00
committed by openshift-cherrypick-robot
parent 8b884ebb61
commit 5972a7d9e4
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
modules/byoh-configuring.adoc
View File

@@ -15,7 +15,7 @@ Any Windows instances that are to be attached to the cluster as a node must fulf
* Port 22 must be open and running an SSH server.
* The default shell for the SSH server must be the link:https://docs.microsoft.com/en-us/windows-server/administration/openssh/openssh_server_configuration#configuring-the-default-shell-for-openssh-in-windows[Windows Command shell], or `cmd.exe`.
* Port 10250 must be open for log collection.
* An administrator user is present with the private key used in the secret set as an authorized SSH key.
* An administrator user is present with the link:https://learn.microsoft.com/en-us/windows-server/administration/openssh/openssh_keymanagement#configure-key-based-authentication[private key used in the secret set as an authorized SSH key] (Microsoft documentation).
* If you are creating a BYOH Windows instance for an installer-provisioned infrastructure (IPI) AWS cluster, you must add a tag to the AWS instance that matches the `spec.template.spec.value.tag` value in the compute machine set for your worker nodes. For example, `kubernetes.io/cluster/<cluster_id>: owned` or `kubernetes.io/cluster/<cluster_id>: shared`.
* If you are creating a BYOH Windows instance on vSphere, communication with the internal API server must be enabled.
* The hostname of the instance must follow the link:https://datatracker.ietf.org/doc/html/rfc1123[RFC 1123] DNS label requirements, which include the following standards: