[Core feature] Allow flytectl to set a targetExecutionCluster
Motivation: Why do you think this is important?
As a follow-up from https://github.com/flyteorg/flyte/issues/5081 this PR adds the ability in flytectl for the user to specify a targetExecutionCluster when creating an execution.
Goal: What should the final outcome look like, ideally?
A user can trigger an execution with flytectl in whatever cluster they want.
Describe alternatives you've considered
N/A
Propose: Link/Inline OR Additional context
No response
Are you sure this issue hasn't been raised already?
- [X] Yes
Have you read the Code of Conduct?
- [X] Yes
To allow flytectl to set a targetExecutionCluster, you need to add support for specifying the ExecutionClusterLabel when creating an execution. This feature enables users to direct executions to specific clusters without being tied to a Project/Domain.
Would you like more detail on how to implement this in flytectl?
Sources:
- RFC: Select cluster execution when triggering an execution
- Configuring cluster resources
- Configuring cluster resources
This is an AI-generated response and your feedback is appreciated! Please leave a 👍 if this is helpful and 👎 if it is not.
Mention @runllm to ask follow-up questions. See runllm.com for more!