Hello, team! I'm deploying Airbyte on EKS. I've gone through this guide. I've following questions, it would be highly appriciated if some can answer them: 1. Should I go with helm chart? or K8S manifests? 2. What are the resource requirements for each component (webapp, temporal service, scheduler etc.)? 3. Worker component is the main component that do heavylifting job. How to benchmark Worker resource requirements? 4. Is there any guidelines on running Airbyte in HA mode? 5. What should be the size of RDS(postgres) instance at the beginning being used as db? Please share any resources/link which can help me. Do mentioned me @Muhammad Imtiaz in the answer. Thanks in advance,

1. Helm Chart is new and can be unstable. Airbyte doesn’t have implemented a good CI workflow to validate every change made to the Chart. If you look for something more stable k8s manifests give this to you, but with less customization. 2. Check the resource limited deployment yaml file: https://github.com/airbytehq/airbyte/blob/master/kube/overlays/stable-with-resource-limits/set-resource-limits.yaml 3. Can you explain what are you trying to achieve with this benchmark? 4. No there isn’t; Airbyte has the guide to deploy in k8s you can use this as starter 5. Check the yaml file I sent to you

Thank you @Marcos Marx (Airbyte). Higly appreciated.