This bug has been verified on OCP 4.8 and passed, thanks. After configured Windows instance, BYOH username encrypted as: # oc get node ip-10-0-152-101.us-east-2.compute.internal -oyaml apiVersion: v1 kind: Node metadata: annotations: k8s.ovn.org/hybrid-overlay-distributed-router-gateway-mac: 00-15-5D-3A-5D-1F k8s.ovn.org/hybrid-overlay-node-subnet: 10.132.3.0/24 machine.openshift.io/machine: openshift-machine-api/sgao-48-nlt75-windows-byoh-us-east-2a-ggs2g volumes.kubernetes.io/controller-managed-attach-detach: "true" windowsmachineconfig.openshift.io/pub-key-hash: 1df2c166b1c401180523270e9cf6bc2cd2724b9279ea65668a3b95298525a0f5 windowsmachineconfig.openshift.io/username: wx4EBwMIp4CKNKbnqfhgmcyYUl+euASXhnZcwAtt+yjS5gE/SD3XXEpGRKP6FMY6<wmcoMarker>3OT+3sg18hri9bEu+a++S9KBlA99QYeuz9bD+bPv7wEUuufFGSH3uzv5ZNtDNcji<wmcoMarker>BnvgxgA=<wmcoMarker>=+E2v windowsmachineconfig.openshift.io/version: 3.1.1+cdbcfb7
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Windows Container Support for Red Hat OpenShift 3.1.1 product release), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2021:4710