Hey, For production-ready deployment, how do you manage permissions for developers? Since Flyte does not support RBAC, I’m curious to understand how domains (development, staging, production) are separated in a secure way, not just logically. Thanks!

What is the preferred way to deploy these days? We have been happily using Flyte for a year now but the setup has changed significantly compared to back then and updating to 1.6 is not straightforward. Should we consider the manifests from the recent release as the most authoritative or instead the helm-chart approach from this guide which btw seems to be installing an entirely new application

flyte-binary

that seems to bundle ... well everything? Do you recommend using flyte-binary these days unless one is using a multi-cluster setup?

Hey flyte team im trying to use flyteremote and am running into a SSL error. Peer name is not in peer certification. The documentation doesnt make it exactly clear how to pass in the cert unless I missed something. Is it as simple as passing in the path to the “certificate_chain” option?

Happy Friday, flyte community! Is there a way to use

with_override

or something else to override only task container image without creating a Pod from scratch (I’d prefer to reuse existing pod config but with new image)?

Can anyone give me some pointers for mounting EFS (shared storage) to the flyte task containers? I have a StorageClass and PersistentVolume setup, and now am trying to get the PersistentVolumeClaim created by using the

cluster_resource_manager

templates. My template looks like this, but I never see a pvc created when tasks are running...

- key: ac_project_efs_shared
      value: |
        apiVersion: v1
        kind: PersistentVolumeClaim
        metadata:
          name: efs-shared
          namespace: {{ namespace }}
        spec:
          accessModes:
            - ReadWriteMany
          storageClassName: efs-sc
          resources:
            requests:
              storage: 5Gi
          volumeName: efs-shared

Are the docs regarding Multi cluster deployment up to date? We completed all steps as instructed on EKS, however • flyteadmin became unhealthy, because the cluster-credentials secret is not being mounted correctly to

/var/run/credentials

in the

sync-cluster-resources

init container. • syncresources also became unhealthy, because the secret was not being mounted to the service at all (as far as we could tell) That being said, after solving both steps manually we eventually saw some life signs on our data plane cluster. However the

flytepropeller

service on the data plane cluster didn’t seem to be able to reconcile the workflow correctly, instead referencing a non existing flyteadmin service.

E0216 14:41:48.783203 1 workers.go:102] error syncing 'flytesnacks-development/f9f0589cf97c949c892f': Workflow[] failed. ErrorRecordingError: failed to publish event, caused by: EventSinkError: Error sending event, caused by [rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp: lookup flyteadmin on 10.100.0.10:53: no such host"]

Is there a full working example? What are we missing? Or would anyone from the community be up for an exchange, if you have succeeded to do the multi cluster setup? For final background: • We aim for the multi cluster setup for operational reasons, but mostly for data isolation. That way we can isolate customer data on a cluster and AWS account level.

What is the recommended way to share curated flows / tasks within an organisation? To add more perspective: In kubeflow we built a bunch of premade components (basically a bit of code + container) that we could load into any pipeline and use in any pipeline. Does something like this exist in Flyte? Best case still executable locally?

Is there any way to define a

ContainerTask

with a toleration or affinity? It looks like I may have define a custom

Task

that overrides the pod spec construction method right now?

I'm not sure how to pass secrets through map_task. I've tried putting the annotation on the task I pass to map_task in addition to passing them to the map_task call itself. Is this related to my issue above? This in not a blocker for me.

hello all, I have

remote = FlyteRemote(
    config=Config.for_endpoint(endpoint='localhost:30080'),
    default_project="flytesnacks",
    default_domain="development",
)

flyte_wf = remote.fetch_workflow(
    name="flyte.workflows.extract_flyte.extract_drs_data",
    project="flytesnacks",
    domain='development',
)