You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
in this, the screenshot is missing the route info:
So a user will be likely to not make anything external.
So their endpoint will look like:
And then, the notebook validation will fail.
In spite of allowed for self-signed certs in the code, it works well with the route, but not at all with the internal endpoint.
The text was updated successfully, but these errors were encountered:
Is there a bug filed against the OpenShift AI? In reproducing this, the behavior is different before and after creating a model server with an external route. If you create the internal service never having created an external service, it will fail with a connection reset. If you create the internal service after an external service exists, it works as expected. Leads me to believe that there's an issue with how the internal routing is set up in the project that the external routing initializes correctly.
Another issue is that while the external endpoint had a verified ssl cert, the internal service does not. This seems like very strange and inconsistent behavior. It makes using these endpoints internally cumbersome even if it works.
I'm following:
https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/2.13/html/openshift_ai_tutorial_-_fraud_detection_example/deploying-and-testing-a-model#deploying-a-model-single-model-server
in this, the screenshot is missing the route info:
So a user will be likely to not make anything external.
So their endpoint will look like:
And then, the notebook validation will fail.
In spite of allowed for self-signed certs in the code, it works well with the route, but not at all with the internal endpoint.
The text was updated successfully, but these errors were encountered: