8000 config.load_kube_config drops into random `sh` shell instead of progressing · Issue #2342 · kubernetes-client/python · GitHub
[go: up one dir, main page]
Skip to content

config.load_kube_config drops into random sh shell instead of progressing #2342

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.

Sign up for GitHub

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

Jump to bottom
Open
faali1 opened this issue Feb 3, 2025 · 2 comments
Open

config.load_kube_config drops into random sh shell instead of progressing #2342

faali1 opened this issue Feb 3, 2025 · 2 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@faali1
Copy link
faali1 commented Feb 3, 2025

What happened (please include outputs or screenshots):

Hello! I'm seeing a regression in the latest verion where when I try to config.load_kube_config(context="cluster_id"), instead of proceeding with the command, it drops me into a random sh shell. When I try the same thing on 30.1.0 it works flawlessly. I've tried multiple contexts

Image

What you expected to happen:

Load kubeconfig and allow proceeding to next command

How to reproduce it (as minimally and precisely as possible):
Go into python REPL
perform the two commands from the ss above.

Anything else we need to know?:
Replicated by three people independently

Environment:

  • Kubernetes version (kubectl version):
Client Version: v1.30.1
Server Version: v1.30.8-eks-2d5f260

  • OS (e.g., MacOS 10.13.6):
    Mac OS 14.7.3

  • Python version (python --version)
    Python 3.8.18

  • Python client version (pip list | grep kubernetes)
    v32.0.0
@faali1 faali1 added the kind/bug Categorizes issue or PR as related to a bug. label Feb 3, 2025
@roycaihw
Copy link
Member

I think this may be related to #2334

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@roycaihw @k8s-ci-robot @k8s-triage-robot @faali1
0