Hey guys hope you are doing well, my name is Nishk...
# ask-the-community
Hey guys hope you are doing well, my name is Nishkal and I am contacting you regarding few doubts on the flyte-config file. A little background about me, I work for a company called OneConvergence which is into building MLOps solutions and we are trying to incorporate flyte to our platform. I have followed the instructions on below url https://docs.flyte.org/en/v1.0.0/deployment/aws/manual.html for manual installation of flyte in eks cluster but except for using the amazon load balancer I used nginx controller for ingress. So my question is in flyte config file which is as below ''' admin: # For GRPC endpoints you might want to use dns:///flyte.myexample.com endpoint: dns///localhost38081 insecureSkipVerify: true # only required if using a self-signed cert. Caution: not to be used in production insecure: true # only required when using insecure ingress. Secure ingress may cause an unavailable desc error to true option. logger: show-source: true level: 0 ''' instead of rpc call i.e. the endpoint of admin which is using dns I want to use something with https endpoint: https://xxxxxxxxxxxxxxxxxxxxxxxxxxx.us-west-2.elb.amazonaws.com/flyteadmin something like the above, is there any way to implement this, because following the installation procedure I am able to get the console page up but not able to create a project as I get the below error when i Use the endpoint with https Error: Connection Info: [Endpoint: https://xxxxxxxxxxxxxxxxxxxxxxx.us-west-2.elb.amazonaws.com/flyteadmin, InsecureConnection?: true, AuthMode: ClientSecret]: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp: address tcp///xxxxxxxxxxxxxxxxx.us-west-2.elb.amazonaws.com/flyteadmin: unknown port" I will really appreciate if you can help me or at least redirect it to some one who as this knowledge. Thanks and have a great day ahead.
@Nishkal Gupta welcome to the Flyte community, I'm glad you're considering Flyte for your platform. What you'd put in
would be typically either a CNAME record that points to your Ingress URL or directly the Ingress URL. It doesn't typically include
Based on the
guide, and with collaboration from the community, we produced a guide that should help you during the deployment process on EKS: https://github.com/davidmirror-ops/flyte-the-hard-way/tree/main It uses the ALB Ingress Controller, but annotations can be ported over to Nginx
Also, if you're doing
kubectl port-forward
, then the
should be just
, without the `dns`portion