Replies: 1 comment
-
[UPDATE]
But they don't see to be correctly defined in contrast with the configuration setting in
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I'm currently trying to deploy Netbox on my kubernetes cluster using the helm chart.
I'd like to use external separate postgresql and redis instances. To do so, I included them in my chart's dependencies:
Now I followed the documentation of Netbox's helm chart saying if you got an external redis instance you need to defined enabled = false under the
redis
key.So I did the following:
And deployed everything. Redis seems to be deployed just fine but when I trying reaching the Netbox page, I get the error :
Error 111 connecting to localhost:6379. Connection refused.
, error that also happens at some point in the netbox pod start.Thing is, I can't find what was wrongly defined as the configuration doesn't seem to be correctly applied to netbox and it still uses the default
localhost
one to reach redis...By going exec into the netbox pod and printing its env variable I can see for example:
NETBOX_REDIS1_MASTER_SERVICE_HOST=<Service_IP>
which I guess means the config is still transfered somewhere...Anyone can help ?
Beta Was this translation helpful? Give feedback.
All reactions