We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
version 32.0.0 fails to parse kube config file properly
kube_config.py fails to parse kubeconfig file. line 520: Object of type ConfigNode is not JSON serializable
What you expected to happen: It should be able to parse old kubeconfig files, this works fine in 31.0.0
How to reproduce it (as minimally and precisely as possible): I can't attach my kubeconfig because I don't have good way to obfuscate it
Anything else we need to know?:
Environment:
Kubernetes version (kubectl version):
kubectl version
kubectl version Client Version: v1.32.1 Kustomize Version: v5.5.0 Server Version: v1.31.5-gke.1023000
OS (e.g., MacOS 10.13.6): MacOs 14.6.1
Python version (python --version) Python 3.9.18
python --version
Python client version (pip list | grep kubernetes) 32.0.0
pip list | grep kubernetes
The text was updated successfully, but these errors were encountered:
Same issue as #2334
Sorry, something went wrong.
Closing as a duplicate of #2334
No branches or pull requests
version 32.0.0 fails to parse kube config file properly
kube_config.py fails to parse kubeconfig file.
line 520: Object of type ConfigNode is not JSON serializable
What you expected to happen:
It should be able to parse old kubeconfig files, this works fine in 31.0.0
How to reproduce it (as minimally and precisely as possible):
I can't attach my kubeconfig because I don't have good way to obfuscate it
Anything else we need to know?:
Environment:
Kubernetes version (
kubectl version
):OS (e.g., MacOS 10.13.6):
MacOs 14.6.1
Python version (
python --version
)Python 3.9.18
Python client version (
pip list | grep kubernetes
)32.0.0
The text was updated successfully, but these errors were encountered: