Samuel Bentley
05/03/2023, 10:45 AMFLYTE_CONFIG=~/.flyte/config.yaml pyflyte run --remote workflows/greeting.py wf --name Sam
Go to <http://localhost:8089/console/projects/flytesnacks/domains/development/executions/fd724a646bd6342cab6c> to see execution in the console.
And when I go to the console, it again shows a grpc error. Any idea what I'm doing wrong. Looks like some connection issueKetan (kumare3)
David Espejo (he/him)
05/03/2023, 2:17 PMkubectl get svc -n flyte ?
Also the contents of your config.yaml
please
The most recent charts now create two services , one for grpc and one for http so if that's the case, you should be running two port-forwarding sessions (one for each service)
Depending on the results I'll update the guideSamuel Bentley
05/03/2023, 2:31 PMkubectl get svc -n flyte
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
flyte-backend-flyte-binary ClusterIP 172.20.91.16 <none> 8088/TCP,8089/TCP 4h37m
flyte-backend-flyte-binary-webhook ClusterIP 172.20.96.142 <none> 443/TCP 4h37m
config.yaml (same one we used for dev)
admin:
# For GRPC endpoints you might want to use dns:///flyte.myexample.com
endpoint: localhost:8089
authType: Pkce
insecure: true
logger:
show-source: true
level: 0
David Espejo (he/him)
05/03/2023, 3:51 PMconfig
file and change the port to 8088
before going to consoleSamuel Bentley
05/03/2023, 4:11 PMDavid Espejo (he/him)
05/03/2023, 4:17 PM8088
as the port in config
is that you receive a Trying to connect an http1.x server