OLS-1561: OLS Requires Secret Even When RHOAI Does Not

Author: rh-tokeefe

Diff for: modules/ols-creating-lightspeed-custom-resource-file-using-cli.adoc

@@ -53,19 +53,20 @@ spec:
   llm:
     providers:
     - credentialsSecretRef:
-        name: openai-api-keys
+        name: rhelai-api-keys <1>
       models:
       - name: models/<model_name>
       name: rhelai
       type: rhelai_vllm
-      url: <URL> <1>
+      url: <URL> <2>
   ols:
     defaultProvider: rhelai
     defaultModel: models/<model_name>
     additionalCAConfigMapRef:
       name: openshift-service-ca.crt
 ----
-<1> The URL endpoint must end with `v1` to be valid. For example, `\https://http://3.23.103.8:8000/v1`. 
+<1> By default the OpenAI API requires a token as part of the request. If your {rhelai} configuration does not require a token you must set the token value to any valid string for the request to authenticate.
+<2> The URL endpoint must end with `v1` to be valid. For example, `\https://http://3.23.103.8:8000/v1`. 
 +
 .{rhoai} CR file
 [source,yaml,subs="attributes,verbatim"]
@@ -78,17 +79,18 @@ spec:
   llm:
     providers:
     - credentialsSecretRef:
-        name: openai-api-keys
+        name: rhoai-api-keys <1>
       models:
       - name: <model_name>
       name: red_hat_openshift_ai
       type: rhoai_vllm 
-      url: <url> <1>
+      url: <url> <2>
   ols:
     defaultProvider: red_hat_openshift_ai
     defaultModel: <model_name>
 ----
-<1> The URL endpoint must end with `v1` to be valid. For example, `\https://<model_name>.<domain_name>.com:443/v1`. 
+<1> By default the OpenAI API requires a token as part of the request. If your {rhoai} configuration does not require a token you must set the token value to any valid string for the request to authenticate.
+<2> The URL endpoint must end with `v1` to be valid. For example, `\https://<model_name>.<domain_name>.com:443/v1`. 
 +
 .{azure-openai} CR file
 [source,yaml,subs="attributes,verbatim"]

Diff for: modules/ols-creating-lightspeed-custom-resource-file-using-web-console.adoc

@@ -55,17 +55,18 @@ spec:
   llm:
     providers:
     - credentialsSecretRef:
-        name: openai-api-keys
+        name: rhelai-api-keys <1>
       models:
       - name: models/<model_name>
       name: rhelai
       type: rhelai_vllm
-      url: <URL> <1>
+      url: <URL> <2>
   ols:
     defaultProvider: rhelai
     defaultModel: models/<model_name>
 ----
-<1> The URL endpoint must end with `v1` to be valid. For example, `\https://http://3.23.103.8:8000/v1`. 
+<1> By default the OpenAI API requires a token as part of the request. If your {rhelai} configuration does not require a token you must set the token value to any valid string for the request to authenticate.
+<2> The URL endpoint must end with `v1` to be valid. For example, `\https://http://3.23.103.8:8000/v1`. 
 +
 .{rhoai} CR file
 [source,yaml,subs="attributes,verbatim"]
@@ -78,17 +79,18 @@ spec:
   llm:
     providers:
     - credentialsSecretRef:
-        name: openai-api-keys
+        name: rhoai-api-keys <1>
       models:
       - name: <model_name>
       name: red_hat_openshift_ai
       type: rhoai_vllm 
-      url: <url> <1>
+      url: <url> <2>
   ols:
     defaultProvider: red_hat_openshift_ai
     defaultModel: <model_name>
 ----
-<1> The URL endpoint must end with `v1` to be valid. For example, `\https://<model_name>.<domain_name>.com:443/v1`. 
+<1> By default the OpenAI API requires a token as part of the request. If your {rhoai} configuration does not require a token you must set the token value to any valid string for the request to authenticate.
+<2> The URL endpoint must end with `v1` to be valid. For example, `\https://<model_name>.<domain_name>.com:443/v1`.
 +
 .{azure-openai} CR file
 [source,yaml,subs="attributes,verbatim"]