[V2][sandbox] Sandbox support webhook

[popojk]

Motivation: Why do you think this is important?

Sandbox should support webhook

Goal: What should the final outcome look like, ideally?

n/a

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?

• Yes

Have you read the Code of Conduct?

• Yes

[runllm]

Currently, Flyte's sandboxed orchestrator is designed to securely execute pure Python control flow and dispatch work to containerized tasks, but it does not natively support running web servers or webhook endpoints directly inside the sandboxed environment. The sandbox restricts network access, OS access, and does not allow arbitrary imports or running persistent services, which are required for webhook support. This is a deliberate security feature to ensure untrusted code cannot expose network endpoints or interact with the outside world from within the sandboxed orchestrator itself, as detailed in the sandboxing documentation and workflow sandboxing in Flyte.

If you need webhook support, the recommended pattern is to deploy a Flyte app (e.g., using FastAPI) outside the sandbox, which can securely trigger Flyte tasks or workflows via the Flyte SDK. This approach is documented in the Flyte app usage patterns and webhook examples. Would you like more detail on how to implement this pattern or on the sandbox's security model?

Sources:

• Flyte app usage patterns
• Webhook examples
• sandboxing documentation
• workflow sandboxing in Flyte

---

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!