🐛 Fix envtest process stop on Windows#3519
Conversation
|
|
|
Welcome @gologames! |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: gologames The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Hi @gologames. 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 Regular contributors should join the org to skip this step. Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions 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. |
|
/ok-to-test |
Fixes #3518
This adds a Windows-specific
signalProcessimplementation for envtest process teardown.On Windows,
os.Process.Signaldoes not supportSIGTERM/SIGKILL, soEnvironment.Stop()fails when stopping the localkube-apiserverandetcdprocesses.The Windows implementation uses
process.Kill()instead.This does not provide full Windows process-tree semantics like Unix process-group signaling. A Windows Job Object would be needed for that. However, in the current envtest setup,
kube-apiserverandetcdare started directly viaexec.Command. Killing those direct child processes fixes the current teardown failure.Tested with an envtest admission webhook suite on Windows.