#4041 Flyte Add Enable/Disable Options for Agent Services Pull request opened by Future-Outlier TL;DR • Added options to enable (default) or disable the Flyte agent. Describe your changes @pingsutw and I have introduced two options for users to configure the Flyte agent - it can now be either enabled or disabled. We believe this enhancement will offer more flexibility and cater to diverse user needs and deployment scenarios. After a thorough consideration, we have decided to set the "enable agent" option as the default setting. Enable agent service (Default) Enable the agent deployment by updating helm and kustomization. You can use my image on the docker hub to test.

cd flyte/docker/sandbox-bundled/
make build
docker tag flyte-sandbox:latest futureoutlier/flyte-sandbox:flyteagent-v2
docker push futureoutlier/flyte-sandbox:flyteagent-v2

./bin/flytectl demo start --image futureoutlier/flyte-sandbox:flyteagent-v2

Disable agent service (Use flag)

./bin/flytectl demo start --image futureoutlier/flyte-sandbox:flyteagent-v2 --disable-agent

Tracking issue #3936 flyteorg/flytectl#420 Check all the applicable boxes ☐ I updated the documentation accordingly. ☑︎ All new and existing tests passed. ☑︎ All commits are signed-off. Screen Shot • New Pod Addition: The newly introduced pod is named "flyteagent". You can view the snapshot of its presence here. • Config Map Update: The "flyte-sandbox-config" config map situated in the "flyte" namespace has been updated. Its current snapshot can be viewed here. Notably, there's an addition of the

enabled-plugins

key, which can be viewed here. flyteorg/flyte GitHub Actions: build-and-push-sandbox-bundled-image ✅ 15 other checks have passed 15/16 successful checks