Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Relax certifi version constraint in the Kubernetes Python client

Offen
#2,733 3 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
2/5
Geschätzter Aufwand
1-3 Stunden
Anfängerfreundlichkeit
35/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
python
Bereich
build-system

Rechercherichtung

The conflict comes from the certifi lower bound added in PR #2660, so start by finding where the package declares its certifi dependency and check that PR's diff. Whether the bound is needed is a maintainer decision, so confirm the intended minimum before editing. Done means pip install kubernetes==37.0.0 certifi==2024.10.17 resolves without error.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

kind/bug

Description

For reasons unrelated to Kubernetes, one of our Python applications requires certifi==2024.10.17 and cannot be upgraded to a later version.
However, we also need to use the latest version of the Kubernetes Python client (kubernetes==37.0.0).

Interestingly, if we force-install both packages together, everything functions correctly with no runtime errors.
However, standard pip installation fails due to a strict dependency constraint.

$ pip install kubernetes==37.0.0 certifi==2024.10.17
ERROR: Cannot install certifi==2024.10.17 and kubernetes==37.0.0 because these package versions have conflicting dependencies.

The conflict is caused by:
    The user requested certifi==2024.10.17
    kubernetes 37.0.0 depends on certifi>=2026.7.22

To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip to attempt to solve the dependency conflict

It appears this restriction was introduced in PR #2660.

Questions / Request

Is this strict lower bound on certifi (>=2026.7.22) strictly necessary for kubernetes==37.0.0?

Would it be possible to relax or widen the certifi version requirement in future releases to accommodate applications locked to slightly older versions, especially since force-installing works smoothly?

What happened (please include outputs or screenshots):

$ pip install kubernetes==37.0.0 certifi==2024.10.17
ERROR: Cannot install certifi==2024.10.17 and kubernetes==37.0.0 because these package versions have conflicting dependencies.

The conflict is caused by:
    The user requested certifi==2024.10.17
    kubernetes 37.0.0 depends on certifi>=2026.7.22

To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip to attempt to solve the dependency conflict

What you expected to happen:

The latest version of kubernetes can be installed successfully together with certifi==2024.10.17.

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

pip install kubernetes==37.0.0 certifi==2024.10.17

Anything else we need to know?:

Environment:

  • Kubernetes version (kubectl version): Client Version: v1.35.9, Server Version: v1.35.0
  • OS (e.g., MacOS 10.13.6): Debian bookworm 12.12
  • Python version (python --version): Python 3.14.0
  • Python client version (pip list | grep kubernetes): 37.0.0
Vorherrschende Sprache
Python
Sterne
7.7k
Forks
3.5k
Ø Merge
1 T. 13 Std.
Gemergte PRs (30 T.)
19

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus kubernetes-client/python

Alle Issues in kubernetes-client/python

Ähnliche Issues

Weitere Issues zu Python

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.