According to completed 'Issues' in the Quarkus project on Github it should be possible to configure Quarkus application to use a predefined Netty threadpool instead of letting Quarkus framework to create it's own.
I have a project based on Quarkus, Vertx and Aws SDK v2 and I want to make sure the netty pool my AWS SDK client uses is the one used by other other libraries.
I want to do this so I can monitor the shared pool and implement my AWS SDK client so that it does not overload the pool by scheduling too many tasks.