Hey, hello! I am curious to hear if anyone else has had this problem, and how you might have solved it. Any and all suggestions are welcome: We are currently using Airflow, and have a per-task allow-list for hosts that a task are allowed to reach on the internet. It will typically look something like this:

t2 = BashOperator(
        task_id='bye_task',
        <SNIPP>
        executor_config={
            "pod_override": k8s.V1Pod(
                metadata=k8s.V1ObjectMeta(annotations={"allowlist": "<http://hooks.slack.com|hooks.slack.com>"})
            )
        },
        <SNIPP>
        )

Naturally, this isn't the prettiest way to declare these kind of required openings. How would you go about solving this in Flyte in the least intrusive way, e.g., we would prefer to avoid leaking the k8s abstractions, which Flyte are very good at avoiding. Would you extend Flyte in some way: https://www.union.ai/docs/flyte/architecture/extending-flyte/, which one, and why? Thank you for your help ❤️

You can use backend pod templates