Closed ujala-singh closed 2 months ago
Hi @ujala-singh !
It looks like the issue is not on the operator side but on your configuration. I don't see any type of extra things the operator should do to allow you to configure the custom path.
As all ingresses are requirering custom annotations it looks hard for me to support all of them.
Summary: Currently, the Temporal Operator does not support custom UI paths, leading to failures when attempting to configure UI paths in the Ingress configuration. This issue causes 404 errors when trying to access the UI through specific paths.
Details: When configuring the Temporal UI using an Ingress with custom paths, the following errors are encountered:
This configuration works without custom paths:
However, when attempting to use custom paths, it fails with the following Ingress configuration:
Impact: The inability to configure custom UI paths limits the flexibility of deploying the Temporal UI behind an Ingress controller, especially in scenarios where the UI needs to be accessible under a specific path or domain structure.
Expected Behavior: The Temporal Operator should support custom UI paths, allowing users to configure and access the Temporal UI under a specified path without encountering 404 errors.
Proposed Solution:
Steps to Reproduce: