Cody Scandore
10/11/2023, 9:56 PM<dns://my-flyte-url.com>
just fine, and connect with a FlyteRemote
instance as well. I am having an issue when trying to connect from inside the EKS cluster, however, since using that endpoint would try to leave the cluster before returning (and the origin IP address is not on the load balancer allowlist).NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/flyte-flyte-binary-grpc ClusterIP 10.100.25.184 <none> 8089/TCP 28d
service/flyte-flyte-binary-http ClusterIP 10.100.25.40 <none> 8088/TCP 28d
service/flyte-flyte-binary-webhook ClusterIP 10.100.141.137 <none> 443/TCP 28d
If so, what would the FlyteRemote config look like, would it be an insecure connection?
flyte_remote = FlyteRemote(
default_domain='development',
default_project='project1',
config=Config.for_endpoint(
endpoint='dns:///flyte-flyte-binary-webhook.flyte.svc.cluster.local',
insecure=True,
)
)
<http://flyte-flyte-binary-http.flyte.svc.cluster.local:8088/api/v1/>...
but the flytekit Remote does not seem to work, or I am not configuring properly.Yee
Thomas Newton
10/16/2023, 10:32 PMendpoint="flyte-flyte-binary-grpc:8089"
with insecure=True
(normally the k8s ingress does the SSL stuff).David Espejo (he/him)
10/17/2023, 7:04 PMdns:///flyte-flyte-binary-grpc.flyte.svc.cluster.local
should at least lead you to the right ClusterIP Service