Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Raise (or make configurable) maxWorkflowSize #1464

Closed
kalugny opened this issue Jul 4, 2019 · 1 comment
Closed

Raise (or make configurable) maxWorkflowSize #1464

kalugny opened this issue Jul 4, 2019 · 1 comment
Milestone

Comments

@kalugny
Copy link

kalugny commented Jul 4, 2019

Is this a BUG REPORT or FEATURE REQUEST?:
Feature request, bordering on bug
What happened:
My workflows fail because they are "too big". What is the reason for the 1MB limit? Can this be raised or made configurable?

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

  • Argo version:
$ argo version
  • Kubernetes version :
$ kubectl version -o yaml

Other debugging information (if applicable):

  • workflow result:
$ argo get <workflowname>
  • executor logs:
$ kubectl logs <failedpodname> -c init
$ kubectl logs <failedpodname> -c wait
  • workflow-controller logs:
$ kubectl logs -n kube-system $(kubectl get pods -l app=workflow-controller -n kube-system -o name)
@sarabala1979
Copy link
Member

#1264 and #1344 will solve the large workflow and 1MB limits on ETCD

@sarabala1979 sarabala1979 added this to the v2.4 milestone Jul 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants