为了更快的定位您的问题，请提供以下信息，谢谢
【详述】使用 starrocks-kubernetes-operator 1.10.2部署 在阿里云k8集群上部署，无法正常启动
【背景】使用阿里云nas配了一个storageClass作存储，调整内存request大小，调大的时候pod都看不见，调小了pod能看见，但是无法通过health check。进入pod内部，手动执行starrocks_be，会报错/opt/starrocks/be/lib/starrocks_be: error while loading shared libraries: libjvm.so: cannot open shared object file: No such file or directory
【业务影响】
【是否存算分离】否
【StarRocks版本】 3.3-latest
【集群规模】 1fe+1be
【联系方式】feng.yu@cyshuju.com
【附件】
check the be logs under /opt/starrocks/be/log/
be.INFO全是下面这样的日志，而且在不停的输出
I0520 17:43:01.057411 27 block_file.cpp:60] open block file success, fd: 63743, path: /opt/starrocks/be/storage/datacache/blockfile_63715.598618725034
I0520 17:43:01.059615 27 block_file.cpp:60] open block file success, fd: 63744, path: /opt/starrocks/be/storage/datacache/blockfile_63716.598618736245
I0520 17:43:01.061908 27 block_file.cpp:60] open block file success, fd: 63745, path: /opt/starrocks/be/storage/datacache/blockfile_63717.598618746797
I0520 17:43:01.064132 27 block_file.cpp:60] open block file success, fd: 63746, path: /opt/starrocks/be/storage/datacache/blockfile_63718.598618756886
I0520 17:43:01.066361 27 block_file.cpp:60] open block file success, fd: 63747, path: /opt/starrocks/be/storage/datacache/blockfile_63719.598618767275
be.WARNING 有这些提示，但我用的是官方的镜像，如果是下面的问题导致的，要修改配置，是否意味着，我需要自己制作一个镜像？
E0520 17:38:21.377421 27 daemon.cpp:244] got signal: Terminated from pid: 0, is going to exit
W0520 17:40:26.150722 27 jit_engine.cpp:144] System or Process memory limit is less than 16GB, disable JIT. You can set jit_lru_cache_size a properly positive value in BE’s config to force enabling JIT
W0520 17:40:26.161720 27 cache_options.cpp:126] fail to clean residual datacache data, reason: /opt/starrocks/be/datacache: No such file or directory
E0520 17:38:21.377421 27 daemon.cpp:244] got signal: Terminated from pid: 0, is going to exit
应该是被kubenetes kill的, 看看pod event和对应的node event, 是不是POD内存用超了或者节点内存不够在开始evict pod.
