Hey, I am trying to use the

clientSecret

authflow to be able to build and register workflows in our GitHub Actions CI builds. I looked at the CI docs here, and getting the following error both locally and in our CI when I run the same command. Has anyone experienced anything similar? Flytectl config available in comments

☁  ~  flytectl get projects
Error: rpc error: code = Unauthenticated desc = transport: oauth2: cannot fetch token: 401 Unauthorized
Response: {"error":"invalid_client","error_description":"Client authentication failed (e.g., unknown client, no client authentication included, or unsupported authentication method)."}

Hey, everyone! Is anyone else having problems starting the sandbox? A coworker of mine was trying to start it using FlyteCTL and was getting this error:

Error: Get "<https://127.0.0.1:30086/api/v1/nodes>": dial tcp 127.0.0.1:30086: connect: connection refused

When she tries to execute the Docker image

<http://cr.flyte.org/flyteorg/flyte-sandbox|cr.flyte.org/flyteorg/flyte-sandbox>

directly with

docker run

, this error happens:

...
Release "flyte-core" does not exist. Installing it now.
Error: file '/root/.cache/helm/repository/flyte-core-v1.1.0.tgz' does not appear to be a gzipped archive; got 'application/octet-stream'

I was able to reproduce it in my machine. What could be happening?

Hi, I'm seeing a very weird error in my workflow (see thread). Propeller is complaining that there is no input to a node in the workflow. When I look into the gcs bucket I see this in the

<gs://mybucket/metadata/propeller/myproject-myns-myexecid/n1/data/>

path:

data
|  0/
|  | start-node/
|  |    |  0/
|  |    |  | outputs.pb
|  
|  inputs.pb

i.e. there's no

n0/

directory under

data/0/

. When I look into

data/0/start-node/0/outputs.pb

it looks to be the correct input to the entire workflow. I'm running

flytekit 1.5.0

and deployed from helm

flyte-core:1.5.0

. I tried reverting to

1.4.0

in the core helm chart but it didn't help. Any idea why this is happening?

Hello, How to configure S3 and Postgres from Environment variables in Kubernetes cluster?

Hey! Why is it necessary to install flytekit in virtual environment. ??? Flytekit not found error occurs even if the module is installed. But it works fine if flytekit is installed in venv and that activated venv is used for workflows and programs.

hi everybody, has anybody running on a mac m1 managed to run the tensorflow cookbook example?

Does anyone have experience with TLS/SSL between the Ingress and Flyte? 🔒 🔒 I’m currently trying to get a reference implementation to work for deploying Flyte on GCP with the GKE Ingress controller (instead of nginx) wich would allow us to use Google Identity Aware Proxy (IAP) for authentication. IAP requires the user to login “at the load balancer”, before a request reaches the backend, instead of being redirected to the login screen by the backend. Because this is more secure it’s a requirement by our company (and actually also my previous one) to use IAP. To make gRPC backends work with the GKE Ingress, HTTP2 needs to be enabled for the backend. Flyte already does so in the gcp helm values. Using HTTP2 between the load balancer and the backend requires TLS between lb and backend. So I’m trying to deploy Flyte with this config:

configmap:
  adminServer:
    server:
      httpPort: 8088
      grpcPort: 8089
      security:
        secure: false #true
        ssl:
          certificateFile: "/etc/tls/cert.pem"
          keyFile: "/etc/tls/key.pem"

Certificate is self-signed and mounted into the flyteadmin pod via a secret. I can’t talk to flyteadmin though and would appreciate help getting this to work 🙂 Details in 🧵

I have two questions: 1. How can I monitor the std out and std err while the task is running ? 2. Does

pyflyte register

not use the docker image when its packaging the workflow. We have some custom dependencies for the workflow to execute that aren’t present in the development environment.

How does development with Flyte compare to Dagster?

Hey guys, I'm trying to pass environment variables to my pods. I'm using flyte-binary deployment. For some reason, the task pods are getting the environment variables with their name lowercased. Other environment values passed by Flyte to the pod are not lowercased, only the added values via the k8s plugin. This is the relevant snippet from the `values.yaml`:

...
configuration
  ...
  inline:
    plugins:
      k8s:
        inject-finalizer: false
        default-env-vars:
          FLYTE_AWS_ACCESS_KEY_ID: "foo"
          FLYTE_AWS_SECRET_ACCESS_KEY: "secret-bar"
          FLYTE_AWS_ENDPOINT: "custom-endpoint"

I logged into the binary pod and located the inline config:

/etc/flyte/config.d/100-inline-config.yaml

. I can clearly see that the

default-env-vars

is not lowercased. I tried a little to locate the relevant Go code but didn't find anything that lower-case the env var names. Thanks for your help!