-
Notifications
You must be signed in to change notification settings - Fork 9
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
Add optional initContainers and volumes #17
Add optional initContainers and volumes #17
Conversation
Signed-off-by: David Young <[email protected]>
Signed-off-by: David Young <[email protected]>
Signed-off-by: David Young <[email protected]>
Signed-off-by: David Young <[email protected]>
Following up from #16, this PR adds the option to include additional initContainers, volumes, and volumeMounts (on the primary container). The use-case here for large tests which required external data. We have about 300MB of files which we upload/download as part of a test, and the easiest way to get these into a loadtest is via an initContainer and an emptyDir mount. This would also satisfy the requests for running tests from configMaps, per #7 |
Add support for initContainer
Signed-off-by: David Young <[email protected]>
Signed-off-by: David Young <[email protected]>
Signed-off-by: David Young <[email protected]>
…flagger-k6-webhook into add-optional-initContainer
Signed-off-by: David Young <[email protected]>
Ugh. I messed up both PRs. Creating 2 clean ones... |
Signed-off-by: David Young [email protected]