[stable/rabbitmq] Auto configure rabbitmq total_memory_available_override_value from chart resources.limits.memory value

[thomas-riccardi]

Is this a request for help?: no

---

Is this a BUG REPORT or FEATURE REQUEST? (choose one): FEATURE REQUEST

Version of Helm and Kubernetes:

• helm v2.7.2
• kubernetes server v1.6.11-gke.0

Which chart:
stable/rabbitmq 0.6.10

What happened:
Memory alarms (https://www.rabbitmq.com/memory.html) could be correctly auto configured using resources.limits.memorychar value with rabbitmq total_memory_available_override_value config (rabbitmq/rabbitmq-server#1234).

Anything else we need to know:
It would be probably easier if bitnami docker image exposed a config for it, but it will probably not happen: https://github.com/bitnami/bitnami-docker-rabbitmq/issues/52 they insist on configuring via config file (which would be hard to merge if the chart user can configure it too in the future (see #2784)).
Or maybe it should all be done in the bitnami image, as it's done in the library/rabbitmq image (docker-library/rabbitmq#196) ?

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

[thomas-riccardi]

/remove-lifecycle rotten

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[stale]

This issue is being automatically closed due to inactivity.