Configure SSL CA CERTIFICATE with REQUESTS_CA_BUNDLE env var before certifi

[nirousseau]

What is the feature and why do you need it:

The idea is to configure ssl_ca_cert using the REQUESTS_CA_BUNDLE env var before falling back to certifi if no specific configuration has been provided.

Some applications that are using kubernetes-client / python do not provide a parameter to client/configuration.py#L83. Using an env var before certifi will help such use cases.

Finally, it can be very useful in a container context, as we can pass this configuration via, once again, env vars.

Describe the solution you'd like to see:

In :
client/rest.py#L70

At the moment, the code is the following :

        # ca_certs
        if configuration.ssl_ca_cert:
            ca_certs = configuration.ssl_ca_cert
        else:
            # if not set certificate file, use Mozilla's root certificates.
            ca_certs = certifi.where()

We can add a new condition of the form :

        # ca_certs
        if configuration.ssl_ca_cert:
            ca_certs = configuration.ssl_ca_cert
        elif 'REQUESTS_CA_BUNDLE' in os.environ:
            ca_certs = environ.get('REQUESTS_CA_BUNDLE')
        else:
            # if not set certificate file, use Mozilla's root certificates.
            ca_certs = certifi.where()

The env var REQUESTS_CA_BUNDLE seems to be a good candidate as it is a common practice.

Related issues:

• Certifi overrides system CA config on RHEL/CentOS #859
• certificate verify failed #1017

[palnabarun]

@nirousseau Why not pass the ssl_ca_cert while initializing configuration?

import os
from kubernetes import client, config

client_configuration = client.configuration.Configuration()
client_configuration.ssl_ca_cert = os.environ.get('REQUESTS_CA_BUNDLE')

config.load_kube_config(client_configuration=client_configuration)

This creates a separation of concern and solves the problem at hand.

Also, changing anything in https://github.com/kubernetes-client/python/blob/master/kubernetes/client/rest.py requires a change in the OpenAPI generator since the module is automatically generated from OpenAPI spec.

[nirousseau]

@palnabarun Hello, thank your for your answer.

For more context, this proposal is connected with this issue from apache / airflow : apache/airflow#8019.

I agree that the responsibility of setting this configuration belongs to the software that is using this library. But as a system administrator, I would like to change this setting, even if the developers of apache / airflow have not integrated the ability to change it.

I want to discuss the idea that both developers and system administrators should be able to change the value of the certificate authority path, or at least, its default value.

Currently : user_given_setting -> certifi.

Developer oriented.

Pros :

• Separation of concern, as only developers can operate the change by editing the code calling the library.

Cons :

• I have to make a fork of apache / airflow and alter the logic
• System administrators are relying on developers to expose this setting

I suggest : user_given_setting -> system_env -> certifi.

Developers + Operators can control the behavior.

Pros :

• Both developers and system administrators can set the default CA path.

Cons :

• Add a few lines in the OpenAPI generator

Now, the question "should a library inspect its environment in order to set default settings ?" can be legitimately asked. This proposal adds more control to system administrators, but it can be a breaking change for systems that have this env var miss configured.

[splashx]

This code snippet:

import os
from kubernetes import client, config

client_configuration = client.configuration.Configuration()
client_configuration.ssl_ca_cert = os.environ.get('REQUESTS_CA_BUNDLE')

config.load_kube_config(client_configuration=client_configuration)

Unfortunately doesn't load the kube config config as expected - for example, the host is set as localhost instead of that of the kubeconfig/context.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[palnabarun]

/lifecycle frozen
/assign