victorious-jelly-28729
04/17/2025, 12:15 PMjolly-florist-66728
04/17/2025, 12:15 PMvictorious-jelly-28729
04/17/2025, 12:18 PMjolly-florist-66728
04/17/2025, 12:18 PMflytectl
command-line tool. Archiving a project will hide it from the Flyte console and prevent further updates or executions, but it will not delete the associated resources. Here's how you can archive a project:
1. Using flytectl
: You can archive a project by specifying its ID with the -p
flag and adding the --archive
flag. For example:
flytectl update project -p my-project-id --archive
2. Using a YAML file: You can also define a YAML file with the project ID and desired updates, including a state field to indicate archiving. The state field should be set to 1
for archived. Then, use the --file
flag to apply the changes:
# update.yaml
id: "my-project-id"
state: 1
flytectl update project --file update.yaml --archive
For managing resources manually, you would need to handle the cleanup of Kubernetes namespaces and other resources outside of Flyte. This might involve using Kubernetes commands to delete namespaces or other resources associated with the project. However, be cautious as manual deletion can lead to unintended consequences if not done carefully.
Would you like more detailed guidance on managing specific resources manually?
Sources:
- flytectl update project 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.victorious-jelly-28729
04/20/2025, 4:16 AMjolly-florist-66728
04/20/2025, 4:16 AMflyteadmin
configuration and the cluster resource configuration
. Here's a general approach:
1. Update flyteadmin
Configuration: You would need to remove the entries for the production and staging domains from the domain.yaml
file in the flyteadmin
configuration. This file typically lists all the domains that Flyte recognizes.
2. Update Cluster Resource Configuration: Similarly, you should update the cluster resource configuration to remove any references to the production and staging domains. This might involve editing the cluster_resources.yaml
or equivalent configuration files where domain-specific resources are defined.
After making these changes, Flyte should not create namespaces or resources for the production and staging domains, as they will no longer be recognized as valid domains. However, it's important to ensure that all workflows and tasks are updated to not reference these domains, as this could lead to errors.
Would you like more detailed guidance on editing these configuration files or managing the transition?
Sources:
- https://github.com/flyteorg/flyte/pull/1440
- https://github.com/flyteorg/flyte/blob/master/charts/flyte-core/values.yaml 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.