Virtuoso has some specific entries in its configuration (namely virtuoso.ini file).
I believe that this parameter is the ResultSetMaxRows parameter, currently set in -1.
It seems that -1 does not mean "unlimited" but it refers to a 10,000 limit.
Can you provide us with a dump file and a query to try to reproduce this?

According to http://docs.openlinksw.com/virtuoso/dbadm/#ini_SPARQL

ResultSetMaxRows = number . This setting is used to limit the number of the rows in the result. The effective limit will be the lowest of this setting, SPARQL query 'LIMIT' clause value (if present), and SPARQL Endpoint request URI &maxrows parameter value (if present).

I think you should remove the ResultSetMaxRows parameter for unlimited results.

Thank you both for your speedy responses. ;-)
I will remove the ResultSetMaxRows parameter first and see if it helps.

I have updated the docker image that initializes Virtuoso. Now the ResultSetMaxRows parameter is removed.
Please, give it a try and tell us if it works.

Please accept my apologies for the delay in responding. I've just found some time to test it.
Unfortunately, removing the ResultSetMaxRows parameter appears to not change the limit on the number of results. The number of rows in the result. is still 10000. :-(

I suspect that since KOBE uses a cache to speed up endpoint deployment, your installation maybe keeps the old virtuoso configuration in the cache. I suggest to try the following steps and tell us if the problem persists.

First, delete everything (dataset servers, benchmarks, etc.)

kubectl delete experiments.kobe.semagrow.org --all
kubectl delete benchmarks.kobe.semagrow.org --all
kubectl delete federatortemplates.kobe.semagrow.org --all
kubectl delete datasettemplates.kobe.semagrow.org  --all

Then, delete also the cache

kubectl delete pod kobenfs

And finally, re-deploy your KOBE specifications as previously.

Hi @antru6 , that's it! The issue has now been resolved by using the updated docker images for Virtuoso.
Thanks a lot for your help.

Thanks again @chengsijin0817 for identifying this issue and for the tests you have done for us!