Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion modules/byoh-configuring.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down