Skip to content
This repository was archived by the owner on Feb 22, 2022. It is now read-only.
This repository was archived by the owner on Feb 22, 2022. It is now read-only.

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

@thomas-riccardi

Description

@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) ?

Metadata

Metadata

Assignees

No one assigned

    Labels

    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions