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
But using kubernetes operator in unit tests is very taxing on the 4C/16gb Github Runner device. If I want to write integration tests for doris, I need to first start a k3s cluster with docker via testcontainers-java, and then deploy doris's kubernetes operator on the k3s cluster, which almost certainly causes out of memory issues on the Github Runner device because shardingsphere also resident additional hotspot vm processes or graalvm native image processes on the Github Runner device.
It would be nice if these two Docker Images have self-descriptive text to describe how to use them. This would avoid dynamically downloading binaries and generating Docker Images in the context of testcontainers-java, and also avoid starting a k3s cluster.
The text was updated successfully, but these errors were encountered:
4C
/16gb
Github Runner device. If I want to write integration tests for doris, I need to first start ak3s
cluster with docker viatestcontainers-java
, and then deploy doris's kubernetes operator on thek3s
cluster, which almost certainly causesout of memory
issues on the Github Runner device because shardingsphere also resident additionalhotspot vm
processes orgraalvm native image
processes on the Github Runner device.selectdb/doris.fe-ubuntu
andselectdb/doris.be-ubuntu
. But neither of these two Docker Images has self-descriptive text.testcontainers-java
, and also avoid starting ak3s
cluster.The text was updated successfully, but these errors were encountered: