You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, to run the integration tests on kubernetes, we are creating a persistent volume, a job mounting the volume and saving the test results into it, and a final pod mounting the same volume from which we copy the result from.
In fact, with kubernetes, we cannot copy a file from a stopped container in a pod (while this is possible with docker). This issue is tracked in kubernetes/kubectl#454 which has been opened in April 2018, and its priority raised in June 2019 (so not really active...).
But there may be other solution to solve this issue of getting the test results from a kubernete job:
mounting minio or s3 from the test job and getting the results from it after
posting the test results as part of the test job
other?
The text was updated successfully, but these errors were encountered:
Currently, to run the integration tests on kubernetes, we are creating a persistent volume, a job mounting the volume and saving the test results into it, and a final pod mounting the same volume from which we copy the result from.
In fact, with kubernetes, we cannot copy a file from a stopped container in a pod (while this is possible with docker). This issue is tracked in kubernetes/kubectl#454 which has been opened in April 2018, and its priority raised in June 2019 (so not really active...).
But there may be other solution to solve this issue of getting the test results from a kubernete job:
The text was updated successfully, but these errors were encountered: