Currently the Batch Job created by the Operator does not define CPU or Memory request/limits. Consequently, customers that have quotas set which require limits/requests set as mandatory field will not be able to utilise Batch CRs.

We should allow users to define the resource request/limits via the Batch CR, e.g:

apiVersion: infinispan.org/v2alpha1
kind: Batch
metadata: 
  name: mybatch
spec: 
  cluster: infinispan
  configMap: mybatch-config-map
  container: 
    cpu: "2000m:1000m"
    memory: "2Gi:1Gi"

It's also possible to workaround this limitation by defining a Limit Range to ensure that request/limits are automatically defined on the Job pods.