Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for Windows nodes #45

Merged
merged 4 commits into from
Jan 23, 2023
Merged

Conversation

phealy
Copy link
Contributor

@phealy phealy commented Jan 23, 2023

This PR adds support for Windows nodes via a HostProcess pod running PowerShell 7. Doing this relatively cleanly took a little rearranging because certain values needed to be changed based on which operating system was on the node. Whether the node is windows is determined by checking the kubernetes.io/os label on the node object - it defaults back to Linux (with unchanged behavior) unless that label exists and is equal to windows, so this shouldn't cause problems for existing users.

This will work on Kubernetes clusters of at least version 1.23 (where HostProcess containers went beta) with nodes running Windows Server 2019 or Windows Server 2022.

I changed the version in the script to 1.7.0 as a best guess, but obviously feel free to modify as needed.

Copy link
Owner

@kvaps kvaps left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Amazing work, thank you.
As can I see work is still in progress. I will merge it tomorrow, when you stop pushing new commits 🙂

kubectl-node_shell Outdated Show resolved Hide resolved
@kvaps kvaps merged commit 4717bd2 into kvaps:master Jan 23, 2023
@phealy phealy deleted the phealy/node-shell-windows branch January 23, 2023 18:18
@kvaps
Copy link
Owner

kvaps commented Jan 23, 2023

Merged. krew index updated. Thank you for contribution

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants