Chapter 12. Troubleshooting Windows container workloads

Prerequisites

• You have installed the Windows Machine Config Operator (WMCO) using Operator Lifecycle Manager (OLM).
• You have created a Windows compute machine set.
• You have added the key used in the cloud-private-key secret and the key used when creating the cluster to the ssh-agent. For security reasons, remember to remove the keys from the ssh-agent after use.
• You have connected to the Windows node using an ssh-bastion pod.

Procedure

• Access the Windows node by running the following command:

  $ ssh -t -o StrictHostKeyChecking=no -o ProxyCommand='ssh -A -o StrictHostKeyChecking=no \
      -o ServerAliveInterval=30 -W %h:%p core@$(oc get service --all-namespaces -l run=ssh-bastion \
      -o go-template="{{ with (index (index .items 0).status.loadBalancer.ingress 0) }}{{ or .hostname .ip }}{{end}}")' <username>@<windows_node_internal_ip> 

  1

  2

  where:

  <username>

  Specifies the cloud provider username, such as Administrator for Amazon Web Services (AWS) or capi for Microsoft Azure.

  <windows_node_internal_ip>

  Specifies the internal IP address of the node, which can be discovered by running the following command:

  $ oc get nodes <node_name> -o jsonpath={.status.addresses[?\(@.type==\"InternalIP\"\)].address}

Prerequisites

• You installed the Windows Machine Config Operator (WMCO) using Operator Lifecycle Manager (OLM).
• You have created a Windows compute machine set.
• You have added the key used in the cloud-private-key secret and the key used when creating the cluster to the ssh-agent. For security reasons, remember to remove the keys from the ssh-agent after use.
• You have connected to the Windows node using an ssh-bastion pod.