Configuring Internal Termination

Depending on your deployment (CSD or RPM), use one of the following sets of instructions to configure internal termination.

Internal Termination
An internal termination proxy will be run by Cloudera Data Science Workbench's built-in load balancer, called the ingress controller, on the master host.
Private Key and Certificate Requirements
The TLS certificate issued by your CA must list both, the Cloudera Data Science Workbench, as well as a wildcard for all first-level subdomains.
Configuring Custom Root CA Certificate
If your organization uses its own custom Certificate Authority, CDSW engines will not be able to automatically recognise the custom CA's root certificate. This topic describes how to add your internal root CA certificate to CDSW so that it is inserted into the engine's root certificate store every time a session (or any workload) is launched. This will allow processes inside the engine to communicate securely with the ingress controller.
Creating a Certificate Signing Request (CSR) and Key/Certificate Pair
Use the following steps to create a Certificate Signing Request (CSR) to submit to your CA. Then, create a private key/certificate pair that can be used to authenticate incoming communication requests to Cloudera Data Science Workbench.
CSD Deployments
Provides steps to configure internal termination in a CDS deployment.
RPM Deployments
Provides steps to configure internal termination in a RPM deployment.

Parent topic: Enabling TLS/SSL for Cloudera Data Science Workbench