https://flyte.org logo
Join Slack
Powered by
Hi community, i do have a problem with maximum mem...
# flyte-support
r
Hi community, i do have a problem with maximum memory allowed for a task: 
details = "Requested MEMORY limit [3000Mi] is greater than current limit set in the platform configuration [1Gi]. Please contact Flyte Admins to change these limits or consult the configuration"
I tried changing the limits in my values.yaml for my flyte-binary deployment: 
# resources Resource limits and requests for Flyte container
 
# Uncomment and update to specify resources for deployment
 
resources:
requests:
memory: 2Gi
cpu: 500m
limits:
memory: 4Gi
cpu: 1
My version should be 1.8.0 (what helm says). Console UI does not show a version for Admin I updated a couple of days ago and thought maybe https://github.com/flyteorg/flyteadmin/pull/517 should fix my problem, but it seems it did not change a lot
a
@refined-lunch-94030 what's the output of 
kubectl describe cm flyte-backend-flyte-binary-config -n flyte
? This is to validate the actual limits un your Helm deployment
r
Hey @average-finland-92144 Sorry for the lengthy printout. I also removed the database and auth part for security reasons.
Copy code
~|⇒ kubectl describe cm flyte-backend-flyte-binary-config -n flyte
Name:         flyte-backend-flyte-binary-config
Namespace:    flyte
Labels:       <http://app.kubernetes.io/instance=flyte-backend|app.kubernetes.io/instance=flyte-backend>
              <http://app.kubernetes.io/managed-by=Helm|app.kubernetes.io/managed-by=Helm>
              <http://app.kubernetes.io/name=flyte-binary|app.kubernetes.io/name=flyte-binary>
              <http://app.kubernetes.io/version=1.16.0|app.kubernetes.io/version=1.16.0>
              <http://helm.sh/chart=flyte-binary-v1.8.0|helm.sh/chart=flyte-binary-v1.8.0>
Annotations:  <http://meta.helm.sh/release-name|meta.helm.sh/release-name>: flyte-backend
              <http://meta.helm.sh/release-namespace|meta.helm.sh/release-namespace>: flyte


000-core.yaml:
----
admin:
  clientId: flytepropeller
  endpoint: localhost:8089
  insecure: true
catalog-cache:
  endpoint: localhost:8081
  insecure: true
  type: datacatalog
cluster_resources:
  standaloneDeployment: false
  templatePath: /etc/flyte/cluster-resource-templates
logger:
  show-source: true
  level: 5
propeller:
  create-flyteworkflow-crd: true
webhook:
  certDir: /var/run/flyte/certs
  localCert: true
  secretName: flyte-backend-flyte-binary-webhook-secret
  serviceName: flyte-backend-flyte-binary-webhook
  servicePort: 443
flyte:
  admin:
    disableClusterResourceManager: false
    disableScheduler: false
    disabled: false
    seedProjects:
    - flytesnacks
  dataCatalog:
    disabled: false
  propeller:
    disableWebhook: false
    disabled: false

001-plugins.yaml:
----
tasks:
  task-plugins:
    default-for-task-types:
      container: container
      container_array: k8s-array
      sidecar: sidecar
    enabled-plugins:
    - container
    - sidecar
    - k8s-array
plugins:
  logs:
    kubernetes-enabled: false
    cloudwatch-enabled: true
    cloudwatch-template-uri: <https://eu-central-1.console.aws.amazon.com/cloudwatch/home?region=eu-central-1#logsV2:log-groups/log-group/$252Faws$252Fcontainerinsights$252Fflyte-cluster$252Fapplication$3FlogStreamNameFilter$3Dapplication.var.log.containers.{{.podName}}_{{.namespace}}_{{.containerName}}-{{.containerId}}.log>
    stackdriver-enabled: false
  k8s:
    co-pilot:
      image: "<http://cr.flyte.org/flyteorg/flytecopilot:v0.0.28|cr.flyte.org/flyteorg/flytecopilot:v0.0.28>"
  k8s-array:
    logs:
      config:
        kubernetes-enabled: false
        cloudwatch-enabled: true
        cloudwatch-template-uri: <https://eu-central-1.console.aws.amazon.com/cloudwatch/home?region=eu-central-1#logsV2:log-groups/log-group/$252Faws$252Fcontainerinsights$252Fflyte-cluster$252Fapplication$3FlogStreamNameFilter$3Dapplication.var.log.containers.{{.podName}}_{{.namespace}}_{{.containerName}}-{{.containerId}}.log>
        stackdriver-enabled: false


BinaryData
====

Events:  <none>
a
Thanks for sharing. Well' I don't see here the necessary section to adjust resources. IN any case you can: 1. Add the following to the 
inline
section of your 
values.yaml
file 
inline:
task_resources:
defaults:
cpu: 500m
memory: 500Mi
limits:
cpu: 16
memory: 32Gi
(Adjust the numbers to your needs) 2. Run a `helm upgrade`against your release and then verify the configmap again This would change global defaults/limits
👍 1
a
@average-finland-92144 Can this work for the sandbox?
no luck
7 Views
Open in Slack
PreviousNext
Powered by