Support group memory for jemalloc reporting in Kubernetes deployments

Support for jmalloc reporting in Kubernetes

~"group::memory" are adding features to GitLab rails such that reports are periodially created tracking memory usage over time. We need to make some configuration change to support gathering these reports until the feature matures where reports are dropped in Object Storage

Plan of Action

Leverage the emptyDir feature of Kubernetes and create a volume where reports can be placed. We perform this in a few steps as the feature is still under development.

Tracking feature: gitlab-org/gitlab!91283 (merged)

See that issue for further details and analysis of the impacts to performance.

Milestones

• Supporting configuration is pushed into staging
• Feature is working in Staging
  • ENV variable to enable is added
  • FF is enabled - gitlab-org/gitlab#367845 (closed)
• Supporting configuration is pushed into production
• Confirmation all is well in the production environment
  • ENV variable to enable is added
  • FF is enabled - gitlab-org/gitlab#367845 (closed)