Open JuroOravec opened 4 months ago
Ok, I found that the config file is loaded depending on the NODE_ENV
env var, and that currently NODE_ENV
env var is NOT used for anything else in this project. So I was able to fix this by explicitly setting NODE_ENV=production-docker
, so that the config file generated by helm chart is used.
So my updated values.yaml
file looks like so:
replicaCount: 1
serviceAccount:
create: true
# THIS WAS ADDED!
env:
- name: NODE_ENV
value: "production-docker"
connections:
local_production_json:
noSave: false
noLogData: false
# ui:
# foldingChar: "|"
redis:
readOnly: true
# server:
# clientMaxBodySize: "500kb"
# httpAuth:
# username: "the-user"
# password: "is-secret"
connections:
- label: "redis"
host: "redis-master.redis.svc.cluster.local"
port: "6379"
password: 'MY_PASSWORD'
dbIndex: 0
So, now that there's a solution, how can we fix this?
Could we at minimum add this information to the Helm chart README?
Or better yet, update the chart to configure the NODE_ENV
env var automatically?
Let me know your thoughts and I can make the changes if it's simple changes.
Problem:
I'm not able to configure Redis connection through helm chart via
connections.local_production_json
. I wanted to useconnections.local_production_json
so I can configure multiple connections with passwords.Context:
I used the helm chart v0.6.0 to deploy Redis Commander.
I set the
values.yaml
file based on the example like so:Click to toggle values.yaml
```yaml replicaCount: 1 serviceAccount: create: true connections: local_production_json: noSave: false noLogData: false # ui: # foldingChar: "|" redis: readOnly: true # server: # clientMaxBodySize: "500kb" # httpAuth: # username: "the-user" # password: "is-secret" connections: - label: "redis" host: "redis-master.redis.svc.cluster.local" port: "6379" password: 'MY_PASSWORD' dbIndex: 0 ```I confirmed that the configmap resource was successfully created
I confirmed that the configmap was successfully mounted
At this point, the UI was showing only connection
local (localhost:6739:0)
. This is NOT the connection I defined inlocal_production_json
.I verified that the connection in my
values.yaml
file was correct by manually adding it:After I manually added the connection, it was added to the
local-production.json
And here's example what the logs look like at the point where I manually added the connection. All the connection errors are coming from trying to conenect to
localhost:6739:0
, which I did NOT configure: