How can ensure if a particular plugin is actually installed properly. I followed this doc to install tensorflow-operator but after installation when I tried to launch the example workflow mentioned in the doc, I see below error in my flyteworkflow deployment.

message: >-
    failed at Node[n0]. RuntimeExecutionError: failed during plugin execution,
    caused by: failed to execute handle for plugin [tensorflow]: found no
    current condition. Conditions: []

I would also have a question with regards to spot instances. We have a subworkflow (workflow within a workflow) which starts tasks on spot nodes (

interruptible=True

). The task then fails with

Last Error: USER::Pod was terminated in response to imminent node shutdown.

The last log from the node where this task is run on is:

Deleting node <node-id> because it does not exist in the cloud provider

So we assume the node is reclaimed by GCP. Does anyone happen to know whether there might be a difference in how interruptible task failures are handled in subworkflows?

I have a long running workflow in which some tasks that should definitely be cached (I checked the tarball containing the code) are not cached 🤯 Does anyone know where I could find any logs that might shed some light on this? Has anyone seen this before?

Hey community, is it possible to use LDAP for authentication, has somebody already done that? We use an OpenLDAP system for authentication at our company and I have a hard time figuring out how or even if that could be integrated into Flyte's authentication system based on OpenID Connect. Would a server like https://canaille.readthedocs.io/en/latest/ be the way to go? Thanks

friendly ping again on @Omar Abdullahi Ahmed: https://github.com/unionai-oss/unionml/issues/15? @Shivay Lamba: https://github.com/unionai-oss/unionml/issues/16 What’s the status of these issues? Do you have the capacity to work on these?

Hey, everyone! I'm trying to execute the Flyte sandbox but this is happening. What could it be?

Deploying Flyte...
Getting updates for unmanaged Helm repositories...
...Successfully got an update from the "<https://googlecloudplatform.github.io/spark-on-k8s-operator>" chart repository
...Successfully got an update from the "<https://kubernetes.github.io/dashboard/>" chart repository
...Successfully got an update from the "<https://charts.bitnami.com/bitnami>" chart repository
Error: can't get a valid version for repositories contour. Try changing the version constraint in Chart.yaml

sorry for so much spam today 😅 for context this is all around upgrading to 1.0. Getting the following issue when registering with pyflyte. see 🧵

I am trying the example present in documentation. Getting the following error

(flyte)  raviraja@ip-192-168-124-8  ~/Desktop/flows/flyte_flows    pyflyte run example.py:wf --n 500 --mean 42 --sigma 2

Usage: pyflyte [OPTIONS] COMMAND [ARGS]...
Try 'pyflyte --help' for help.

Error: No such command 'run'.

(flyte)  raviraja@ip-192-168-124-8  ~/Desktop/flows/flyte_flows    pyflyte --help
Usage: pyflyte [OPTIONS] COMMAND [ARGS]...

  Entrypoint for all the user commands.

Options:
  -c, --config TEXT       Path to config file for use within container
  -k, --pkgs TEXT         Dot separated python packages to operate on.
                          Multiple may be specified  Please note that this
                          option will override the option specified in the
                          configuration file, or environment variable
  -i, --insecure BOOLEAN  Disable SSL when connecting to Flyte backend.
  --help                  Show this message and exit.

Commands:
  init         Create flyte-ready projects.
  local-cache  Interact with the local cache.
  package      This command produces a Flyte backend registrable package...
  serialize    This command produces protobufs for tasks and templates.

run

is not available. Am I missing something? When running normally with

python example.py

it is working fine. I have installed

flytekit==0.32.6

this version.

Hello! I am trying to use my private Docker Registry for node image, it is works in sandbox if executed ‘docker login’. But how it should be done on production cluster with Flyte? Tried to debug and found this line: https://github.com/flyteorg/flytepropeller/blob/6a9c1d4490c94e993b9a859d15c3b436c98af3c2/pkg/apis/flyteworkflow/v1alpha1/nodes.go#L119 as i understand - Propeller is able to read K8s secrets from this field. But how to pass this field via Python FlyteKit? Can i pass them using raw container definition?

Hey, everyone! I need some help understanding what I'm doing wrong. I'm trying out Flyte using the sandbox and flytectl. I'm following the workflow: build the container, serialize tasks, register the tasks. I'm avoiding fast serialization because I'm using a custom Dockerfile that sets the user as non-root, and apparently that breaks the fast registration system (by the way, is this expected? Will this also happen in a remote cluster?). Now, I just created a new task to test Google Cloud integration, called

test_google_cloud

, but the system won't find it: if I try to run it, I'm met with the error

AttributeError: module 'src.flyte.tasks' has no attribute 'test_google_cloud'

. I ran

docker build

again, serialized the tasks again, registered them again, and still nothing. The task is registered, since I can see it on the UI, but the worker can't find it. What is happening?