[Bug]: Configmaps are not properly injected into the pods about helm-charts

[mslagle]

Until this is fixed, I am unable to enable prometheus metrics. Am I able to override the prometheus setting by overriding an environment variable? Should this work?

env:
  NEO4J_server_metrics_prometheus_enabled: true

[harshitsinghvi22]

neo4j:
  name: prometheus
  acceptLicenseAgreement: "yes"
  edition: enterprise
  password: my-password
config:
  server.metrics.prometheus.enabled: "true"

@mslagle the above seems to be working just fine for me with 5.5.0 helm charts

When the above config is provide the admin cluster ip will have the 2004 port opened as well

Also i can see the configs getting populated and can be verified in the browser

[mslagle]

@harshitsinghvi22 can you still also check the /config folder on the actual containers? I will check my local configuration as well, but I dont think the properties for the extended config should be files.

[mslagle]

@harshitsinghvi22 I am still having the issue. The prometheus config is not coming into neo4j. Yes the admin service endpoint is created, however the config never is loaded into neo4j. This causes the admin endpoint not to work since the core application is not exposing metrics.

As you can see, the configmap does have the property there, but because the the volumemounts do not properly load in the configmap data, the extended configs are never loaded.

[harshitsinghvi22]

As I shared the screenshot earlier it's loading perfectly well...not sure if there is some issue with your setup.

I can try and upload a video for you which demonstrate installing the helm charts with Prometheus config in 5.5.0

[harshitsinghvi22]

closing this issue as it is not reproducible and the configs are loading fine