# Flyte Contributors meetup

[](https://hackmd.io/gmwGOpD_TWiyw9_dJ_34Dg?edit)

## Logistics
* **Goal:** Discuss RFCs, features, integrations and major changes with Maintainers and Technical Steering Committee members
* **When:** Every 2 weeks on Thursdays, alternating times:
* 7:00 am PT ([Timezone converter](https://www.worldtimebuddy.com/?qm=1&lid=5809844,2950159,1273294,1816670&h=5809844&date=2024-2-15&sln=7-8&hf=1))
* 11:00 am PT ([Timezone converter](https://www.worldtimebuddy.com/?qm=1&lid=5809844,2950159,1273294,1816670&h=5809844&date=2024-2-15&sln=11-12&hf=1))
* [iCal File](https://lists.lfaidata.foundation/g/flyte-announce/ics/12031983/2145304139/feed.ics)
* [Join the mailing list](https://lists.lfaidata.foundation/g/flyte-announce/join) to receive the invites/updates
* **Where:** [Zoom bridge](https://zoom-lfx.platform.linuxfoundation.org/meeting/92309721545?password=c93d76a7-801a-47c6-9916-08e38e5a5c1f)
* **How:**
#### Agenda template
* Attendees [name, affiliation]
* Welcome new members
* Introduce [new RFCs](https://github.com/orgs/flyteorg/projects/12/views/1)
* Working Groups updates
* New ideas in [the incubator](https://github.com/flyteorg/flyte/discussions/categories/rfc-incubator)
* Community pulse
* Open mic/questions [add your name]

:::info
:information_source: **Reminders**
:::
* All meetings are recorded and posted to Flyte's [YouTube channel]((https://youtube.com/playlist?list=PLmQd1BBY9MWozXmf4NGS8zQK17E5aV8oE))
* The Linux Foundation's [Code of Conduct](https://lfprojects.org/policies/code-of-conduct/) applies to every communication chanel the community uses
* Agenda is open for everyone wanting to ask questions or propose discussion topics
* **Old meeting notes are saved in the [community repo](https://github.com/flyteorg/community/blob/main/minutes/contributors-meetup/contributors-meeting-notes.md)**
:::info
:information_source: **How to stay involved**
:::
* [#contribute](https://flyte-org.slack.com/archives/C04NJPLRWUX) Slack channel
* [Github Discussions](https://github.com/flyteorg/flyte/discussions)
-----
## May 9, 2024
* Attendees [name, affiliation]
* David Espejo (Union)
* Niels Bantilan (Union)
* Eduardo Apolinario (Union)
* Welcome new members
* Introduce [new RFCs](https://github.com/orgs/flyteorg/projects/12/views/1)
* [Project isolation RFC updates](https://github.com/flyteorg/flyte/pull/5204)
* [Elastic plugin UX](https://github.com/flyteorg/flyte/issues/5339)
* New ideas in [the incubator](https://github.com/flyteorg/flyte/discussions/categories/rfc-incubator)
* Open mic/questions [add your name]
* Multi-cluster deployment
* Datacatalog, Ingress and auth on multi-cluster (Fabio)

From [docs](https://docs.flyte.org/en/latest/deployment/deployment/multicluster.html#data-plane-deployment):

            configmap:
              admin:
                admin:
                  endpoint: <your-Ingress-FQDN>:443 #indicate the URL you're using to connect to Flyte
                  insecure: false #enables secure communication over SSL. Requires a signed certificate
              catalog:
                catalog-cache:
                  endpoint: <your-Ingress-FQDN>:443
                  insecure: false

How does auth work if one was to expose datacatalog through the ingress?

NOTES: datacatalog currently doesn't use auth.

* Can cluster labels be specified for projects via the helm values? See [issue](https://github.com/flyteorg/flyte/issues/4029#issuecomment-2100479357). (Fabio)
* When using the cluster in which the control plane is deployed also as a dataplane, it would be nice to use in-cluster credentials. Would you agree if I add such an option? (Fabio)

            configmap:
              clusters:
               clusterConfigs:
               - name: "dataplane_1"
                 endpoint: https://<your-dataplane1-kubeapi-endpoint>:443
                 enabled: true
                 auth:
                    type: "file_path"
                    tokenPath: "/var/run/credentials/dataplane_1_token"
                    certPath: "/var/run/credentials/dataplane_1_cacert"
               - name: "controlplane"
                 inCluster: true  # Proposed flag

Check [here](https://github.com/flyteorg/flyte/blob/c0f5b10777fbdfcf2b08059a270b04f0c60d7678/flyteadmin/pkg/flytek8s/client.go#L57) if flag is set.
* Ownership of plugins. Should there be something like `flytekitplugins.contrib.x` to signal that a plugin is purely community maintained? Then some process to promote out of `.contrib`.
* Support local pip-installable packages in ImageSpec and pyflyte run --remote: https://github.com/flyteorg/flyte/issues/5343