This message was deleted.
# ask-for-helps
Slackbot
09/22/2022, 4:13 AMThis message was deleted.
π 1
π 1
π¦ 1
u
μνκ·(Teddy)
09/22/2022, 4:17 AMWhen I tested it, I replicated it without LB setting, but I'm asking because it seems to work only on port-forwarded pods.
Additionally, may I know the reason why the clientport below is dynamic?
μνκ·(Teddy)
09/22/2022, 4:19 AMIf I want to set LB, should I change the ingress-nginx type to load balancer?
x
Xipeng Guan
09/22/2022, 4:22 AMThank you for your question, this is an Ephemeral port, which is assigned on the client side when TCP creates a connection, please see wikipedia for more details: https://en.wikipedia.org/wiki/Ephemeral_port
π 1
u
μνκ·(Teddy)
09/22/2022, 4:34 AMThank you for your answer.
I am installing yatai and yatai-deployment in a quick installation method and testing the api.
At this time, there is no LB setting, so even if you clone pods or runners, is it right that only the api distributed to pods with port forwarding settings will work?
I did port forwarding in the form below.
kubectl port-forward -n yatai svc/test-deploy 8002:3000 --address 0.0.0.0
x
Xipeng Guan
09/22/2022, 5:10 AMYou can check the network settings in the yatai-deployment installation documentation: https://docs.bentoml.org/projects/yatai/en/latest/installation/yatai_deployment.html#configure-network
Xipeng Guan
09/22/2022, 5:12 AMThanks for your questions, I'll answer some of them here.
In short, yatai does not care about loadbalancer, if you want to access bento deployment outside the cluster, you only need to set ingress class, yatai doesn't care whether the ingress controller service is exposed through the loadbalancer or the node port.
π 1
Xipeng Guan
09/22/2022, 5:15 AMThat means the user needs to make sure the ingress controller is working, yatai just uses it and doesn't care about its configuration
π 1