Allow to ignore container memory setting

[lorenzobenvenuti]

Hi,

we're using Kubedock to run Quarkus tests in Openshift. Quarkus has a feature called "dev services" that allows to transparently start services as containers (it's based on Testcontainers); some of these containers are setting a value for "memory" (i.e. Docker --memory) and when this happens Kubedock overrides requests/limits settings using this value. However, in this way only requests are set and limits are inherited by the cluster LimitRange settings: in case the memory configured for the container is higher than the default limits value, the container won't start. In order to handle this scenario we'd like to have an option to ignore container settings and force Kubedock specific settings (either the default ones, specified as command line arguments, or those set using container labels).
I realize this is a pretty specific use case but I was wondering if other people could benefit from a similar option (something like --ignore-container-memory, default value == false). If you think it could be useful I can try to work on a PR.

Thanks!

lorenzo

[joyrex2001]

Sounds useful, feel free to create a PR. I agree on the --ignore-container-memory suggestion.

[lorenzobenvenuti]

PR here: #115

Thanks!