Introduce more generous resource requests and remove duplicate file

charts/flyte-binary/values.yaml

@@ -234,12 +234,10 @@ deployment:
   # lifecycleHooks Specify hooks to run in Flyte container before or after startup
   lifecycleHooks: {}
   # resources Resource limits and requests for Flyte container
-  # Uncomment and update to specify resources for deployment
-  # resources:
-  #   limits:
-  #     memory: 1Gi
-  #   requests:
-  #     cpu: 1
+  resources:
+    requests:
+      cpu: "4"
+      memory: "4Gi"
   # podSecurityContext Specify security context for Flyte pod
   # See: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/
   podSecurityContext:

docs/deployment/configuration/index.md

@@ -5,22 +5,7 @@
 This section will cover how to configure your Flyte cluster for features like
 authentication, monitoring, and notifications.
 
-````{important}
-The configuration instructions in this section are for the `flyte` and `flyte-core` Helm charts, which is for
-the {ref}`multi-cluster setup <deployment-deployment-multicluster>`.
 
-If you're using the `flyte-binary` chart for the  {ref}`single cluster setup <deployment-deployment-cloud-simple>`,
-instead of specifying configuration under a yaml file like `cloud_events.yaml` in {ref}`deployment-configuration-cloud-event`,
-you'll need to add the configuration settings under the `inline` section in the `eks-production.yaml` file:
-
-```{eval-rst}
-.. literalinclude:: ../../../charts/flyte-binary/eks-production.yaml
-   :language: yaml
-   :lines: 30-41
-   :caption: charts/flyte-binary/eks-production.yaml
-```
-
-````
 
 
 ```{list-table}