Nandakumar Raghu05/13/2023, 7:10 PM
2. When I run
kubectl get pods -n <my-namespace>
I see three services instead of one flyte-binary service -
kubectl get svc -n <my-namespace>
I am following this simple cloud deployment. When I try to port-forward any of the three services, the kubectl command times out.
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE flyte-backend-flyte-binary-grpc ClusterIP 10.100.105.242 <none> 8089/TCP 33m flyte-backend-flyte-binary-http ClusterIP 10.100.202.80 <none> 8088/TCP 33m flyte-backend-flyte-binary-webhook ClusterIP 10.100.196.242 <none> 443/TCP 33m
does not show anything related to flyte.
kubectl get events
David Espejo (he/him)05/15/2023, 3:25 PM
? It's weird that it created the services and not the Pod. Regarding #2 yes, recent chart versions create separate services, this was needed to meet the requirements of some ingress controllers that have specific annotation for each type of traffic (gRPC, http,etc)
Nandakumar Raghu05/17/2023, 7:11 PM