https://flyte.org logo
Powered by
#ask-the-community
Title
# ask-the-community
g

Giacomo Dabisias IT

08/11/2023, 1:50 PM
Hi there! I was able to set up flyte in my eks cluster and the console works fine, but I am failing to run the cli with flytectl (I get an error stating that the service is unavailable). I wanted to check on the server side if the api requests are actually served and see the logs; where would I see those? In the k8s logs of the admin service? Asking since I can't see any logs in the admin pod, so I wonder if the requests are actually getting through.
k

Ketan (kumare3)

08/11/2023, 1:59 PM
I would try to port forward and run it
And if that works then pretty sure it would be ingress problem, as cli uses Grpc
g

Giacomo Dabisias IT

08/11/2023, 2:00 PM
not sure what you mean 😄 do you mean to simply run flytectl form within the cluster? (maybe even from the admin pod on loopback )?
(I also think it's an ingress problem, but wanted to double check)
k

Ketan (kumare3)

08/11/2023, 2:00 PM
No just port forward port 8089 I think using kubectl port forward
g

Giacomo Dabisias IT

08/11/2023, 2:01 PM
isn't it 8088?
k

Ketan (kumare3)

08/11/2023, 2:01 PM
8088 is for http and 8089 for Grpc
But @David Espejo (he/him) knows more haha
g

Giacomo Dabisias IT

08/11/2023, 2:02 PM
interesting. I only see 8088 in the ingress description of the api endpoint
Copy code
/api                                      flyteadmin:80 (10.0.20.18:8088)
/api/*                                    flyteadmin:80 (10.0.20.18:8088)
never mind
Copy code
/flyteidl.service.SignalService           flyteadmin:81 (10.0.20.18:8089)
              /flyteidl.service.SignalService/*         flyteadmin:81 (10.0.20.18:8089)
              /flyteidl.service.AdminService            flyteadmin:81 (10.0.20.18:8089)
              /flyteidl.service.AdminService/*          flyteadmin:81 (10.0.20.18:8089)
              /flyteidl.service.DataProxyService        flyteadmin:81 (10.0.20.18:8089)
              /flyteidl.service.DataProxyService/*      flyteadmin:81 (10.0.20.18:8089)
              /flyteidl.service.AuthMetadataService     flyteadmin:81 (10.0.20.18:8089)
              /flyteidl.service.AuthMetadataService/*   flyteadmin:81 (10.0.20.18:8089)
              /flyteidl.service.IdentityService         flyteadmin:81 (10.0.20.18:8089)
              /flyteidl.service.IdentityService/*       flyteadmin:81 (10.0.20.18:8089)
              /grpc.health.v1.Health                    flyteadmin:81 (10.0.20.18:8089)
              /grpc.health.v1.Health/*                  flyteadmin:81 (10.0.20.18:8089)
I am still not sure what you mean with port forwarding things from kubectl, but I have a call with david later today.
2 Views
Powered by