Couchdb 2.2 brought some changes with how things are initialized and torn down, which caused some ripples. Some of this is incidental: making the certificate management path the same for kubernetes and docker, for example.
An external volume is used for couchdb data in the docker path. We're in a holding pattern for the kubernetes path, as the wiser choice is to use OOTB artifacts for couchdb.
Couchdb 2.2 brought some changes with how things are initialized and torn down, which caused some ripples. Some of this is incidental: making the certificate management path the same for kubernetes and docker, for example.
An external volume is used for couchdb data in the docker path. We're in a holding pattern for the kubernetes path, as the wiser choice is to use OOTB artifacts for couchdb.
This change is