Flyte enables production-grade orchestration for machine learning workflows and data processing created to accelerate local workflows to production.

Flyte

Hi, is there an equivalent section to <https://github.com/flyteorg/flyte/blob/5fc57fa5968c1c10747d6fe57ae7159f5b09fa52/charts/flyte-core/values-eks.yaml#L324-L341|these lines> for setting up notifications in flyte-binary deployment?

I tried setting the following lines under `configuration.inline`
```          notifications:
            emailer:
              sender: flyte-notifications@company.com
              subject: 'Notice: Execution "{{ name }}" has "{{ phase }}" in "{{ domain}}".'
              body: >
                View details at <a href=<http://flyte.abc.com/projects{{> project }}/domains/{{ domain }}/executions/{{ name }}>
            processor:
              accountId: 1234567
              queueName: flyte
            publisher:
              topicName: arn:aws:sns:us-east-1:1234567:flyte
            region: us-east-1
            type: aws```
it took some effect because the flyte-binary pod failed to access sqs at first. So I added the sqs and sns policies to the iam role to fix it.

howerver, there was no message sent to the sqs (and thus slack or email) when I launched workflows with:
```FlyteRemote.execute(
    my_wf,
    options=remote.Options(
        notifications=[
            flytekit.Slack(
                [WorkflowExecutionPhase.ABORTED, WorkflowExecutionPhase.FAILED, WorkflowExecutionPhase.SUCCEEDED],
                ["abc@abc.slack.com"],
            ),
            flytekit.Email(
                [WorkflowExecutionPhase.ABORTED, WorkflowExecutionPhase.FAILED, WorkflowExecutionPhase.SUCCEEDED],
                ["abc@abc.com"],
            ),
        ]
    )
)```

hi! seems like an issue was created sometime ago: <https://github.com/flyteorg/flyte/issues/4024>

I worked around this issue by overwriting the `emailer` section with kustomization after helm templating. My issue seems different. From the aws console I saw flyte-binary is fetching the sqs messages however there was no message sent to the queue when a workflow reached a termination state.