Kuberenetes Python client doesn't work with AWS EKS (Exec plugin) in Windows

[bhaoz]

What happened (please include outputs or screenshots):
Kubernetes Python client doesn't work with AWS EKS in Windows.
I have AWS EKS clusters created and setup. And my environment to testing is Windows OS. When I run config.load_config_file=KUBE_CONFIG_PATH), it works well in other OS but in Windows OS, it shows:

ERROR:root:[WinError 2] The system cannot find the file specified

I identified issue is actually coming from here, in Windows OS seems like we need to have shell=True argument also added when executing command or it will fail

What you expected to happen:
Expect Kubernetes Python Client should work for all platforms

How to reproduce it (as minimally and precisely as possible):

• Follow https://docs.aws.amazon.com/eks/latest/userguide/create-cluster.html to create AWS EKS cluster
• Follow https://docs.aws.amazon.com/eks/latest/userguide/create-kubeconfig.html to update local kubeconfig file
• Run Python interactive program: python
• >>> from kubernetes import config
• config.load_kube_config(config_file="{PATH_TO_THE_KUBECONFIG_FILE")
• Error showing up: ERROR:root:[WinError 2] The system cannot find the file specified

Anything else we need to know?:
Kindly check the code link, I think that's the root cause. Verified that adding shell=True in here make Kubernetes Python client work well to load kubeconfig
in Windows. And did we handle similar things for calling subprocess.Popen in Windows before?

Environment:

• Kubernetes version (kubectl version): Directly using Kubernetes Python client with Version: 30.1.0
• OS (e.g., MacOS 10.13.6): Microsoft Windows [Version 10.0.20348.2655]
• Python version (python --version) Python 3.11.9
• Python client version (pip list | grep kubernetes): 30.1.0

[bhaoz]

Hi there, any updates?

[yliaog]

/help

could you file a PR for the fix? thanks.

[k8s-ci-robot]

@yliaog:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/help

could you file a PR for the fix? thanks.

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.

[Raghul-M]

Hi, should I work on this?