Is your feature request related to a problem? Please describe.
The Bytewax materialization engine needs to support configuration options for more advanced Kubernetes deployments (EKS, GCP, etc) to make it usable at scale.

Describe the solution you'd like
The main configuration options that are needed for the Bytewax materialization job are:

• setting explicit resource requests and limits (rather than relying on platform defaults which may not be enough)
• supporting service accounts and IAM roles
• specifying an image pull secret to support pulling Docker images from Dockerhub, Artifactory, etc

Describe alternatives you've considered
The Kubernetes job that runs is dynamically generated by the bytewax code. Existing configuration options are insufficient.

Additional context
I'd really like to test the Bytewax materialization engine on our instance of EKS. In its current implementation, it's operationally too simple and not usable outside of minikube.