Fix gMSA setup on Windows

[TinaMor]

PR Description

This PR resilves the following issues caused when trying to import registry keys from registerplugin.reg:

1. Error opening the file. There may be a disk or file system error.
2. Failed to open registry key

TL;DR

1. The gMSA setup on WS2025 fails with the error: Error opening the file. There may be a disk or file system error.

   image-builder/images/capi/ansible/windows/roles/gmsa/files/install-gmsa-keyvault-plugin.ps1

   Line 119 in e224d7c

   reg.exe import "registerplugin.reg"

   To resolve the issue, we now use an absolute path to the registerplugin.reg file since it is copied to the same location where the install-gmsa-keyvault-plugin.ps1 script is executed.

   image-builder/images/capi/ansible/windows/roles/gmsa/tasks/gmsa_keyvault.yml

   Line 43 in e224d7c

   dest: "{{ kubernetes_install_path }}"

2. reg.exe import fails with "Failed to open registry key"
   This happens when the registry keys already exist. To resolve this, we parse the registerplugin.reg file (downloaded from kubernetesartifacts.azureedge.net/ccgakvplugin) to identify all the registry keys that will be updated by importing registerplugin.reg, we transfer ownership to the user and then restore it to the original owner.

[k8s-ci-robot]

Hi @TinaMor. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[TinaMor]

/ok-to-test

[k8s-ci-robot]

@TinaMor: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/ok-to-test

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[jsturtevant]

/ok-to-test

[jsturtevant]

/test pull-azure-sigs

[TinaMor]

/test pull-azure-sigs

[jsturtevant]

/test pull-azure-sigs

[jsturtevant]

@TinaMor could you rebase this?

[TinaMor]

/test pull-azure-sigs

[TinaMor]

/test pull-azure-sigs

[jsturtevant]

/test pull-azure-sigs

[TinaMor]

/test pull-azure-sigs

[jsturtevant]

gmsa installer check worked. powershell timedout and should be resolved with #1619

[TinaMor]

/test pull-azure-sigs

[TinaMor]

/test pull-azure-sigs

Edit: sig-windows-2025-containerd: SUCCESS

[mboersma]

/lgtm
/assign @jsturtevant

[jsturtevant]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jsturtevant

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [jsturtevant]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment