This message was deleted.

Hello, can you tell me more? Are you using Yatai?

If you’re using Yatai, the path should be configurable through ingress. cc: @Aaron Pham

I need the serving api url like this; Somedomain.com/myyataibasepath/api1

Yes, ingress can be configured to add a base path. We have users in the community configured similar setup. cc: @Mike Kuhlen

Yes, we set up a k8s VirtualService that handles this re-routing. But really it has nothing to do with Yatai, and is handled at the istio gateway level.

http:
    - match:
        - uri:
            prefix: /<BENTO_NAME>/
      rewrite:
        uri: "/"
      name: <BENTO_NAME>
      route:
        - destination:
            host: <BENTO_NAME>.yatai.svc.cluster.local
            port:
              number: 3000

This makes it so that

https://<OUR_API_GATEWAY_URL>/<BENTO_NAME/

gets re-routed to

<BENTO_NAME>.yatai.svc.cluster.local:3000

.

Each model has its own sub domain. I cannot change the Yatai web generaged url in the Yatai UI. Even though I can add an ingrsss, I cannot change the link in the UI.

@YataiUser001 I don’t think Yatai currently support custom sub-domain for each bento deployment. Both domain suffix and ingress path can be customized, just not at a per bento deployment level. To modify domain-suffix and ingress-path by modifying the configmap in the yatai-deployment namespace.

kubectl edit cm/network -n yatai-deployment

Adding @Xipeng Guan to cross check my answer.

Are there any plans to add the feature in the near future?

It is not on our current roadmap of Yatai. We are happy to jump on a call and hear your use case.

My company does not allow the dynamic sub domain feature. I worry about the webpage is not going to work correctly due to the html css js code's web directory path problem. I have not tried yet though. And I wonder if I can contribute to Yatai project for the feature.

Is your service accessed within the cluster or does it need to be accessed across clusters? If it is accessed within the cluster, you only need to use the internal domain name of k8s service. If you need to access it across clusters, you can consider using istio's VirtualService function or start an nginx service as a gateway.

I access internally as you said. I want to access through web UI too.