-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Doesn't remove old containers (> maxHistory) #15
Labels
Comments
Hi DmitryBe@, This is not yet supported. This option currently just limits the number of workflows that appear in the Kubernetes status when using "kubectl swf get -o yaml. |
hello @vicaire , |
Yes, but this is low priority at this time. |
paveldournov
added
priority/p1
priority/p2
addition/feature
and removed
priority/p2
labels
Nov 5, 2018
Removing old PODs and workflows will be done as part of #844 Resolving as duplicate. |
Linchin
pushed a commit
to Linchin/pipelines
that referenced
this issue
Apr 11, 2023
Install python3 in the Docker image used for our E2E workers.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
does the parameter
maxHistory
assumes removing old argo workflows, or it's just defines number of records inworkflowHistory
?i have following configuration (keep it short for simplicity):
In a
workfloHistory
is see 5 last records:Unfortunately, old containers wasn't removed:
The text was updated successfully, but these errors were encountered: