PATH_TO_CA_BUNDLE env variable could inject a path to a crt that contains authority for pip and conda when pointing on an autosigned enteprise package manager like nexus or artifactory.
We could use it by injecting with some tools like gatekeeper/kyverno but we could also for next steps:
add helm chart supports (giving a value override this env variable)
add onyxia injection support (giving a region configuration inject this path).
Being here the certificat support had to be handle by some injection process with external tools.
To go further:
the helm chart could support a liste of ca to add a configmap with crt mounted in a Path referenced by PATH_To_CA_BUNDLE
onyxia could inject this list of ca in region configuration.
PATH_TO_CA_BUNDLE env variable could inject a path to a crt that contains authority for pip and conda when pointing on an autosigned enteprise package manager like nexus or artifactory.
We could use it by injecting with some tools like gatekeeper/kyverno but we could also for next steps:
Being here the certificat support had to be handle by some injection process with external tools.
To go further: