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

Add optional initContainers and volumes #17

Closed

Conversation

funkypenguin
Copy link
Contributor

Signed-off-by: David Young davidy@funkypenguin.co.nz

Signed-off-by: David Young <davidy@funkypenguin.co.nz>
Signed-off-by: David Young <davidy@funkypenguin.co.nz>
Signed-off-by: David Young <davidy@funkypenguin.co.nz>
Signed-off-by: David Young <davidy@funkypenguin.co.nz>
@funkypenguin
Copy link
Contributor Author

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

Signed-off-by: David Young <davidy@funkypenguin.co.nz>
Signed-off-by: David Young <davidy@funkypenguin.co.nz>
Signed-off-by: David Young <davidy@funkypenguin.co.nz>
…flagger-k6-webhook into add-optional-initContainer
Signed-off-by: David Young <davidy@funkypenguin.co.nz>
@funkypenguin
Copy link
Contributor Author

Ugh. I messed up both PRs. Creating 2 clean ones...

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

Successfully merging this pull request may close these issues.

None yet

1 participant