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

Flyte

Flyte 1 supported many different secret managers: <https://www.union.ai/docs/v1/flyte/deployment/flyte-configuration/secrets/#configuring-a-secret-management-system-plugin|union.ai/docs/…/secrets#…>

I was surprised / shocked when I saw the currently embedded secret manager impl in flyte 2 INLINE the secret vals on env vars as opposed to using `secretRef` or `secretKeyRef`

As an aside, creating the resources used by flyte in k8s has been fraught with pain. I (my llm agent) needed to dig through the source code to figure out how to hash the secret key names, this seems like a pretty important thing to have documented from an operational POV.

are there any plans on supporting declarative configuration of the flyte 2 platform via CRs? I would at least like to export the generated knative objects for apps for archiving or reuse on a separate flyte cluster, but as far as I can tell they won't be "managed" by flyte if created that way

as for the CRs are you talking about Apps?

this pr addresses the issue. will merge it soon
<https://github.com/flyteorg/flyte/pull/7834>

BTW great to meet you <@U0BNREF3XRB> welcome to the community

great turn around! thanks guys, glad to see the fix

<@UNZB4NW3S> Nice to meet you!

> as for the CRs are you talking about Apps?
As an example, I can configure ArgoCD declaratively with CRDs as opposed to <https://argo-cd.readthedocs.io/en/stable/user-guide/projects/#creating-projects|with the CLI> or making api calls. If I want to create a new project in argocd, I can submit an `AppProject` resource to k8s: <https://argo-cd.readthedocs.io/en/stable/operator-manual/declarative-setup/#projects|argo-cd.readthedocs.io/en/stable/operator-manual/declarative-setup#…>

metaflow, which can execute on argo workflows (sep. project from argocd), allows you to export the <https://flyte-org.slack.com/archives/C0BKN1E7494/p1787781237102279|WorkflowTemplate> manifests so they can be managed via gitops: <https://github.com/Netflix/metaflow/pull/2743|github.com/Netflix/metaflow/pull/2743>

This feature would be useful for the apps that are deployed as knative services by flyte.

>  have you been using flyte 2?
Yes, I used flyte 1 for a long time, currently evaluating if v2 is prod ready for my use cases

Given the APIs are there, writing an operator on top can be next. Would that be something you would want to contribute to the community? We would definitely welcome that

That would be fun! I'd love to work on that <@UNW4VP36V>

Hey <@U0BNREF3XRB> just pinging to see if I can offer any help brainstorming/designing