While the service itself does not require them, there are situations that may.
The example at hand is connecting to a JupyterHub instance that uses a custom certificate authority.
To the best of my knowledge there are two solutions:
Create a custom image that contains all the required certificates
Use an init container that will update the system's certs storage with additional certificates
This patch implements the latter as it avoids creating new images just for that purpose and the additional certificates can be easily changed using a central storage.
I added the new fields to the schema but there are several others that are not documented. Since they are unrelated to this change, should they be added in a separate MR ?
While the service itself does not require them, there are situations that may.
The example at hand is connecting to a JupyterHub instance that uses a custom certificate authority.
To the best of my knowledge there are two solutions:
This patch implements the latter as it avoids creating new images just for that purpose and the additional certificates can be easily changed using a central storage.