Add option to disable strict x509 verifcation in sync client

[m1racoli]

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.

[yliaog]

/help

[k8s-ci-robot]

@yliaog:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

Details

In response to this:

/help

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[yliaog]

Sure, please.

/assign @sajjadghf

[opulentgrip]

How will the implementation of disable_strict_ssl_verification ensure compatibility with the existing ssl.VERIFY_X509_STRICT flag in scenarios where both are set in kubernetes.client.configuration.Configuration?

[gerhardwimmer80]

How will the implementation of disable_strict_ssl_verification ensure it does not conflict with existing settings in kubernetes.client.configuration.Configuration, particularly with ssl.VERIFY_X509_STRICT already enabled?

[deleahlenaya26]

How will the proposed implementation handle the ssl.VERIFY_X509_STRICT flag in scenarios where both it and disable_strict_ssl_verification are configured in kubernetes.client.configuration.Configuration?

[Vishwa0223]

i want to work so pls assign to me

[yliaog]

/assign @Vishwa0223