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
Feedback from the domain experts is that both the resource-catalogue and data-access can be configured with ingress that uses path-prefix style routing. The resource-catalogue configured must also include the full URL, so that the dynamic links provided by the api will be presented as needed.
I'm not sure the existing helm charts fully support this ingress configuration - to be checked.
Use path-based ingress rules instead of host-based, for example:
example.com/workspace/resource-catalogue instead of resource-catalogue.workspace_name.example.com
The problem is that wildcard SSL certificate are only valid for first level domains.
The text was updated successfully, but these errors were encountered: