@ancient-wolf-19325 In flyte-core helmchart https://github.com/flyteorg/flyte/blob/master/charts/flyte-core/values.yaml I found a way to set

projectQuotaCpu

per domain. Helmchart itself does not show how to set it up per project. Is it even possible?

Setting

projectQuotaCpu

per domain is supported directly in the Flyte-core Helm chart via the

cluster_resource_manager.config.cluster_resources.customData

field, but setting it per project (within a domain) is not natively supported in the Helm values file. The Helm chart only allows you to specify quotas at the domain level, not at the project+domain granularity. This is confirmed by the structure in values.yaml and related config examples, which only nest quotas under domains, not projects. For per-project quotas, you must use Flyte's dynamic resource management features after deployment, such as updating settings via

flytectl

or the FlyteAdmin API, as discussed in this issue. The Helm chart does not provide a direct way to set project-level quotas at install time. Sources: - Flyte Issue #2070 - values.yaml 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

@ancient-wolf-19325 how about

task_resource_defaults

- any way of setting different task resources for specific projects?

No, the Flyte-core Helm chart's

task_resource_defaults

only sets global (platform-wide) defaults and limits for all tasks; it does not support per-project overrides via the values.yaml file. To set different task resources for specific projects, you must use Flyte's matchable resource system after deployment, typically via

flytectl update task-resource-attribute

or the FlyteAdmin API, as described in Flyte Issue #2070 and the overridable defaults RFC. The Helm chart and values.yaml do not provide a mechanism to specify project-level task resource defaults at install time; this must be managed post-deployment. Sources: - Flyte Issue #2070 - RFC: Sane overridable defaults 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

@ancient-wolf-19325 I have setup

initial-project

in helmchart and removed one of the projects that was already used. Will it be removed and will all runs from it be removed or do I have to make manual steps?

No, removing a project from

initialProjects

in the Helm chart does not delete the project or its runs from Flyte. The

initialProjects

field only seeds projects at install time; it does not manage or remove existing projects or their data. Manual steps are required to archive or clean up projects and their executions, as Flyte does not support project deletion via Helm or the API—only archiving is supported, and data remains unless explicitly cleaned up, as discussed in Flyte Issue #1619 and Flyte Issue #3234. Would you like more detail on how to archive or clean up projects and their data? Sources: - Flyte Issue #1619 - Flyte Issue #3234 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

@ancient-wolf-19325 how to cleanup the project and remove it entirely

Flyte does not support fully deleting a project and all its resources via the API or CLI; only archiving (tombstoning) is supported, which hides the project but does not remove its data or executions. Complete removal would require manual deletion from the database and object storage, which is not recommended and can lead to inconsistencies, as discussed in Flyte Issue #1619 and Flyte Issue #3234. If you need to fully remove a project, you must manually delete all related database entries and storage objects, but this is risky and not officially supported. Would you like more detail on the manual cleanup process and its risks? Sources: - Flyte Issue #1619 - Flyte Issue #3234 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

@ancient-wolf-19325 ok so how to archive the project

To archive a project in Flyte, use the command-line tool

flytectl

with the

update project --archive

flag. For example:

flytectl update project -p <project-id> --archive

This will mark the project as archived, making it hidden in the UI and unavailable for new executions, but it will not delete any data. For more details, see Flyte Issue #1619 and Flytectl project update docs. Would you like more detail on archiving or unarchiving projects? Sources: - Flyte Issue #1619 - flytectl update project command 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

@ancient-wolf-19325 how do I get project_id If I get the name of it

You can retrieve the project ID by listing all projects with

flytectl get project

, which displays both the project name and ID. For example:

flytectl get project

This will show a table with columns for ID, NAME, and DESCRIPTION, allowing you to match the name to its corresponding ID. For more, see Flytectl get project. Would you like more detail or examples? Sources: - flytectl get project command 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

@ancient-wolf-19325 can a new run be submitted to archived project?

No, you cannot submit a new run to an archived project. Once a project is archived, it is treated as inactive and new executions, updates, or registrations are blocked, as described in Flyte Issue #1619 and Flyte Issue #569. Would you like more detail on the behavior of archived projects? Sources: - Flyte Issue #569 - Flyte Issue #1619 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

@ancient-wolf-19325 can I control project description via helmchart? or only via flytectl

You cannot control or update a project description via the Helm chart after initial creation; the Helm chart's

initialProjects

only seeds project names/IDs at install time and does not manage descriptions. To set or update a project description, you must use

flytectl

or the FlyteAdmin API, as shown in flytectl create project and flytectl update project. Would you like more detail on using

flytectl

to manage project descriptions? Sources: - flytectl create project command - flytectl update project command 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

@ancient-wolf-19325 give me example of exact command that updates description of single project using flytectl

To update the description of a single project using flytectl, run:

flytectl update project -p <project-id> --description "New project description"

Replace

<project-id>

with your project's ID. This command updates only the description field. For reference, see flytectl update project command. Sources: - flytectl update project command 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

@ancient-wolf-19325 how can i setup RBAC so only few people can update projects but more people can submit jobs? is there a way to do that

Currently, Flyte open source does not support fine-grained RBAC (Role-Based Access Control) for restricting who can update projects versus who can submit jobs. All authenticated users can access all projects and perform actions like submitting workflows or updating projects, as discussed in Flyte Issue #5189, Flyte Issue #3909, and Flyte Issue #555. There are ongoing discussions and proposals for RBAC, but no official support is available in open source Flyte as of now. Would you like more detail on current workarounds or the status of RBAC proposals? Sources: - Flyte Issue #5189 - Flyte Issue #3909 - Flyte Issue #555 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.