Flyte enables production-grade orchestration for machine learning workflows and data processing created to accelerate local workflows to production.

Flyte

image.png

i'm able to use flyte perfectly fine on an EKS cluster. but on our in-house cluster I'm having trouble with getting signed urls. does anyone know of anyway to track this down a little deeper? - the only catch is nginx manages 30080 and 30443 not 80/443
I'm using: FLYTE_SDK_LOGGING_LEVEL=10
and i get:
19:41:09.910042 INFO     raw.py:64 - Flyte Client configured -&gt; <http://flyte.cluster.company.com:30443|flyte.cluster.company.com:30443> in secure
                         mode.
+ the shown image

with the config:
```---
admin:
  endpoint: dns:///flyte.cluster.company.com:30443
  insecure: false
console:
  endpoint: <https://flyte.cluster.company.com:30443/console>```


solved. I ended up writing a short python script instead of using pyflyte run to see if that gave me better logs. the python script let me know that this was an openssl error. our certificates are boutique so I had to mess around handcrafting one. then to get flyte(grpc) to actually use it it had to set the path to the cert to: GRPC_DEFAULT_SSL_ROOTS_FILE_PATH