You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there! I'm testing the Helm CouchDB chart. Everything works fine, but I have a doubt. The kocolosk/couchdb-statefulset-assembler sidecard is running forever for each node in the cluster. I think it is not necessary because if we scale up the new node will run a new sidecar and it will automatically join the cluster. Does make sense to kill the sidecar after the node was joined to the cluster? So we free resources like RAM and CPU
The text was updated successfully, but these errors were encountered:
Hi there! I'm testing the Helm CouchDB chart. Everything works fine, but I have a doubt. The kocolosk/couchdb-statefulset-assembler sidecard is running forever for each node in the cluster. I think it is not necessary because if we scale up the new node will run a new sidecar and it will automatically join the cluster. Does make sense to kill the sidecar after the node was joined to the cluster? So we free resources like RAM and CPU
The text was updated successfully, but these errors were encountered: