Currently the resources for the external dependencies InitContainer are undefined. Consequently, if a LimitRange is in affect for the deployment namespace than the InitContainer will always be restricted to these resource values. This can cause issues, such as OOM, if the LimitRange is too small for JVM based processes.

To workaround such scenarios, we should allow users to have full control of the InitContainer resource configuration by exposing it in the Infinispan CR as follows:

spec: 
  dependencies: 
    initContainer: 
      cpu: "2000m:1000m"
      memory: "2Gi:1Gi"