From dfc002d1c2f990677b28636c13850fa39ea7c94d Mon Sep 17 00:00:00 2001 From: Ravi Srinivasan Date: Thu, 1 Feb 2024 08:43:57 +0530 Subject: [PATCH] fix text to clarify HTTP->HTTPS redirection (#37) --- modules/chapter2/pages/section2.adoc | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/modules/chapter2/pages/section2.adoc b/modules/chapter2/pages/section2.adoc index db5b13f..1758cf2 100644 --- a/modules/chapter2/pages/section2.adoc +++ b/modules/chapter2/pages/section2.adoc @@ -214,7 +214,7 @@ You interact with this container when you use the JupyterLab web interface. * The `oauth-proxy` container, which provides authorization and authentication to access JupyterLab. -RHOAI also creates the required services and routes to enable HTTP and HTTPS traffic into the workbench container. +RHOAI also creates the required services and route to allow external traffic into the workbench container. If you list the resources of the OpenShift namespace that corresponds to your data science project, you should see something similar to this: [subs=+quotes] @@ -234,6 +234,11 @@ NAME ... *route.route.openshift.io/my-first-workbench* ... ---- +[NOTE] +==== +A single HTTPS route is created with non-secure traffic (HTTP port 80) configured to be redirected to the HTTPS port 443 (`insecureEdgeTerminationPolicy: Redirect`). +==== + Creating a new persistent storage in RHOAI results in the creation of a PersistentVolumeClaim (PVC) in the corresponding OpenShift project. The following diagram represents the OpenShift resources involved in a workbench: