What resources do I need for Flyte deployment?

[SandraGH5]

I’m listing all the resources needed by Flyte to be deployed:

• PostgreSQL database, required for FlyteAdmin and DataCatalog components

• S3 for object storage, required by FlyteAdmin, FlytePropeller and DataCatalog

• AWS SQS queue for the event scheduler

Is there anything that I’m missing? I checked the doc (which is really nice now btw ✨) and I didn’t see anything else but I just want to make sure that I’m not missing anything.
We had to deploy Ambassador for something else for example and that was a bit of a surprise.

Stephan.

[SandraGH5]

The minimum requirements are - rds, s3 and kubernetes. Also either a cluster wide role or if you prefer to use Iam roles then Iam for service accounts or Kiam.
Then you need a way to talk to FlyteAdmin and data catalog. This can use multiple options on AWS:

1. Elb
2. Alb
3. Contour
4. Plain envoy
   And then once you venture in the deeper end you need: SQS, SNS, and cloudwatch cron scheduler.

We have a helm template now to deploy. We also have kustomize.
It is recommended to deploy Flyte to an entire cluster instead of shared (but sharing is ok) this is easy to get started.

Also you should have ability to pull containers from GitHub registry, and SES if you want to send notification emails.

@kumare3
@wild-endeavor