kubernetes-client/python

Add option to disable strict x509 verifcation in sync client

Open

#2,602 opened on May 27, 2026

View on GitHub
 (5 comments) (0 reactions) (1 assignee)Python (3,323 forks)batch import
help wantedkind/feature

Repository metrics

Stars
 (6,225 stars)
PR merge metrics
 (Avg merge 10d 3h) (2 merged PRs in 30d)

Description

What is the feature and why do you need it:

Since Python 3.13 RFC 5280 compliance is strictly enforced by default with the ssl.VERIFY_X509_STRICT flag. While kubernetes.aio.client.configuration.Configuration does have the option disable_strict_ssl_verification it is still missing for kubernetes.client.configuration.Configuration.

Describe the solution you'd like to see:

Implement patches for kubernetes.client.configuration.Configuration and kubernetes.client.rest.RESTClientObject to add support for disable_strict_ssl_verification similar to how it's been handled for the async client.

Contributor guide

Research direction
Study the async client implementation of disable strict ssl verification in Configuration and RESTClientObject, then replicate the same changes in the sync client's Configuration and RESTClientObject classes, ensuring compatibility with Python 3.13+.
Tech stack
python
Domain
apicloudbackend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
PythonKubernetesSSL
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75