This repository has been archived by the owner on Feb 22, 2022. It is now read-only.
[pull-charts-e2e] CI needs to work well with stateful applications #1724
Labels
lifecycle/rotten
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Is this a request for help?:
Is this a BUG REPORT or FEATURE REQUEST? (choose one): Feature Request
Version of Helm and Kubernetes:
Which chart:
Could impact all stateful set charts
What happened:
Statefulset charts with multiple replicas tend to start one after the other, some statefulset also has initContianers configured, e2e CI job fails for these types of workloads which might need longer duration to come up. Currently the CI waits for 3 mins.
What you expected to happen:
We should either give a very long time such as
10mins
to allow the stateful applications to come upor
Should find a better way to test stateful applications in the ci.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know:
cc: #1721
The CI used to wait for 2 mins, we recently increased it to 3mins still doesn't help.
The text was updated successfully, but these errors were encountered: