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

k8s_sdk29.0 error:no attribute 'BatchV1beta1Api' #2246

Open
Rettpa opened this issue Jun 6, 2024 · 4 comments
Open

k8s_sdk29.0 error:no attribute 'BatchV1beta1Api' #2246

Rettpa opened this issue Jun 6, 2024 · 4 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@Rettpa
Copy link

Rettpa commented Jun 6, 2024

What happened (please include outputs or screenshots):
from kubernetes import client, config
config.load_kube_config('token//xxxx.conf')
k8s_api = client.BatchV1beta1Api()

AttributeError: module 'kubernetes.client' has no attribute 'BatchV1beta1Api'

k8s version = 1.20
k8s sdk version = 29.0.0

Environment:

  • Kubernetes version (kubectl version):
  • k8s1.20
  • OS (e.g., MacOS 10.13.6):
  • Python version (python --version)
  • python3.6
  • Python client version (pip list | grep kubernetes)
  • 29.0.0
@Rettpa Rettpa added the kind/bug Categorizes issue or PR as related to a bug. label Jun 6, 2024
@showjason
Copy link
Contributor

There is a significant version mismatch between k8s and k8s sdk, you can downgrade the version of k8s sdk or upgrade version of k8s.

@Rettpa
Copy link
Author

Rettpa commented Jun 19, 2024

There are both new and old versions of k8s, and the new version of sdk is not compatible

@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 Sep 17, 2024
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough active 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 rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

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

/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

4 participants