Use nssm for kubelet log rotation on Windows

[jsturtevant]

What this PR does / why we need it:

When installing kubelet via nssm we still used kubelets built in logging. The built in logger logs duplicated data two three different files streams which isn't useful since it duplicates data and the error/warning files don't have enough context in them.

Since we already use nssm we can use the built in log redirection and logging will be much simpler to reason about and contain less information. The log files will still be in the same location.

This also turns on kubelet to Automatic so it will boot automatically on restart (#554)

Which issue(s) this PR fixes (optional, in fixes #(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged): Fixes #554

Additional context
Add any other context for the reviewers

[jsturtevant]

/sig windows
/assign @perithompson

[jsturtevant]

hmm the pip install failed here too, we may need an updated pip in ci?

�[0;32m    sig-ubuntu-1804-gen2: fatal: [default]: FAILED! => {"changed": false, "cmd": ["/usr/bin/pip3", "install", "azure-cli"], "msg": "stdout: Collecting azure-cli\n  Downloading https://files.pythonhosted.org/packages/ba/5a

/retest

[jsturtevant]

failure was ubuntu:

�[0;32m    sig-ubuntu-2004-gen2: fatal: [default]: FAILED! => {"changed": false, "cmd": "/usr/bin/apt-key add -", "msg": "Warning: apt-key output should not be parsed (stdout is not a terminal)\ngpg: can't connect to the agent: IPC connect call failed", "rc": 2, "stderr": "Warning: apt-key output should not be parsed (stdout is not a terminal)\ngpg: can't connect to the agent: IPC connect call failed\n", "stderr_lines": ["Warning: apt-key output should not be parsed (stdout is not a terminal)", "gpg: can't connect to the agent: IPC connect call failed"], "stdout": "", "stdout_lines": []}�[0m

Windows passed: 1;32m==> sig-windows-2022-containerd: Goss validate ran successfully�[0m

/retest

[jsturtevant]

flake with prow reading the Azure secrets

/retest

[jsturtevant]

packer crashed:

�[1;31mBuild 'sig-windows-2019' errored after 29 minutes 17 seconds: unexpected EOF�[0m

==> Wait completed after 29 minutes 17 seconds

==> Some builds didn't complete successfully and had errors:
--> sig-windows-2019: unexpected EOF

==> Builds finished but no artifacts were created.
panic: runtime error: invalid memory address or nil pointer dereference
2021/12/15 19:56:10 packer-builder-azure-arm plugin: [signal SIGSEGV: segmentation violation code=0x1 addr=0x50 pc=0x1a933ce]
2021/12/15 19:56:10 packer-builder-azure-arm plugin: 
2021/12/15 19:56:10 packer-builder-azure-arm plugin: goroutine 42 [running]:
2021/12/15 19:56:10 packer-builder-azure-arm plugin: github.com/Azure/go-autorest/autorest/azure.(*Future).WaitForCompletionRef(0xc000788cc0, 0x546d9c0, 0xc0008740c0, 0x53f6420, 0xc000e74f80, 0x540e140, 0xc000dbcc90, 0xc000e83ac0, 0xc0012646e0, 0xdf8475800, ...)
2021/12/15 19:56:10 packer-builder-azure-arm plugin: 	/home/circleci/project/packer/vendor/github.com/Azure/go-autorest/autorest/azure/async.go:174 +0x54e

I don't see anything in this pr that would cause this will run again then investigate if it happens again...

/retest

[jsturtevant]

created issue for Ubuntu pip error: #766

/retest

[perithompson]

ah this looks much better, ive want to have that auto for a while but the logs always stopped me, thank @jsturtevant

/lgtm

[knabben]

should this be configurable and defaulted to this value if not passed?

[knabben]

we can improve it on another PR..

[knabben]

/lgtm

[jsturtevant]

/assign @codenrhoden @CecileRobertMichon

[CecileRobertMichon]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: CecileRobertMichon, 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:

• images/capi/OWNERS [CecileRobertMichon]

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