https://flyte.org logo
#ask-the-community
Title
# ask-the-community
m

Mohd Shahid Khan Afridi

02/06/2023, 3:08 PM
We are setting up flyte in GCP, is ingress and FQDN a mandatory requirement for a production ready setup? can we can run the jobs without having a FQDN?
k

Ketan (kumare3)

02/06/2023, 3:55 PM
They are not mandatory, but thr ui uses rest api and cli uses Grpc. If you are using the single binary setup you should be able to Simply port forward
Cc @jeev
j

jeev

02/06/2023, 5:11 PM
👍
i can confirm that you can run flyte on GCP entirely internal to the k8s cluster and port-forward as necessary if registering tasks/workflows or viewing the console.
m

Mohd Shahid Khan Afridi

02/07/2023, 6:34 AM
Also could anyone please refer me to some doc which talks about how a continuous integration and continuous deployment look like for a flyte based ml-workflows ?
a

Alex Papanicolaou

02/14/2023, 6:50 PM
@Mohd Shahid Khan Afridi did you ever find a solution to this? Running into the same problem.
m

Mohd Shahid Khan Afridi

02/15/2023, 5:09 AM
@Alex Papanicolaou I was able to utilise the port forwarding inorder to make flyte cli work with remote cluster. For UI console port forwarding didn't help I started using dns
a

Alex Papanicolaou

02/15/2023, 5:17 AM
Thanks @Mohd Shahid Khan Afridi. I did the same with DNS. Thanks for confirming.
I was able to utilise the port forwarding inorder to make flyte cli work with remote cluster
I have been struggling to get
flytectl
to work with the DNS name and the ingress so I’m going to try this instead since I just got it working on the simple
flyte-binary
deployment.
m

Mohd Shahid Khan Afridi

02/15/2023, 5:22 AM
I also faced error connecting flytectl with dns host, for now I am skipping certificate verification by adding below config in my config.yaml file to make it work
Copy code
admin:
 # For GRPC endpoints you might want to use dns:///flyte.myexample.com
 insecure: false
 insecureSkipVerify: true
78 Views