#3631 feat: allow seedProjects to be set via inline configuration Pull request opened by ossareh Tracking issue Closes #3545 Describe your changes Add a

SeedProjects

key to the Admin configuration struct in

cmd/single

. This allows users to specify which projects should be created at start up. This allows management of the flyte installation to be more declarative via the helm chart installation path. Check all the applicable boxes ☑︎ I updated the documentation accordingly. ☑︎ All new and existing tests passed. ☑︎ All commits are signed-off. Note to reviewers The original ticket suggests that

configuration.admin.seedProjects

should be settable; however, that key doesn't exist in the current setup. Instead this works in the same way one can set task_resources, via `configuration.inline`:

# values.yaml
flyte-core-components:
  admin:
    seedProjects:
      - flytesnacks
      - flytemeals

In my local sandbox:

POD_NAMESPACE=flyte go run -tags console cmd/main.go start --config ~/.flyte/local-dev-config.yaml

with a

~/.flyte/local-dev-config.yaml

containing:

flyte:
  admin:
    seedProjects:
      - flytesnacks
      - flytemeals

Results in: I haven't run this in a cluster; I'm not entirely sure how to do so easily. I see some infrastructure for k3s (which I've not used), but I cannot find docs on how to use that to validate this change. Reading deployment.yaml leads me to believe this should work with the proposed values.yaml above. flyteorg/flyte GitHub Actions: build-and-push-sandbox-bundled-image GitHub Actions: sandbox-bundled-functional-tests GitHub Actions: build-and-push-single-binary-image ✅ 9 other checks have passed 9/12 successful checks