I just noticed a Config disabled notice within the CouchDB Fauxton interface of our multi-node CHT setup (running on K3s) and I’m looking for some clarification.
Specifically, I see this notice when navigating to:
- Config:
_utils/#/_config - User Management (Change Password):
_utils/#/changePassword
In both cases, I’m redirected to _utils/#cluster/disabled with the following message:
Config disabled
It seems that you are running a cluster with 3 nodes. For CouchDB 2.0 or greater we recommend using a configuration management tools like Chef, Ansible, Puppet or Salt (in no particular order) to configure your nodes in a cluster.
We highly recommend against configuring nodes in your cluster using the HTTP API and suggest using a configuration management tool for all configurations.
Under _utils/#/setup, it says:
Apache CouchDB is configured for production usage as a single node!
Our CHT environment consists of three worker nodes and one control plane node using K3s. We recently upgraded from CHT version 4.12.0 to 4.17.0. I’m unsure if this notice was present before the upgrade.
My questions are:
- Is this “Config disabled” notice expected behavior in a multi-node CHT environment on K3s?
- Does this notice indicate a potential misconfiguration or a need for further action on our part?
- Specifically, in the context of CHT on K3s, are there recommended configuration management tools or best practices for managing CouchDB settings?
- Are there any potential implications or security concerns associated with this notice that we should be aware of?
- Is it possible that the upgrade from 4.12.0 to 4.17.0 caused this change?
Any insights or guidance on this would be greatly appreciated.
Thanks!