The custom startup command was causing CouchDB to crash during initialization.
The official couchdb:3.3 image has a proper entrypoint that handles all setup
correctly using environment variables.
Changes:
- Removed custom command/entrypoint override
- Rely on official CouchDB image's built-in initialization
- Increased probe delays and failure thresholds for stability
- Liveness: initialDelay 60s, failureThreshold 6
- Readiness: initialDelay 30s, failureThreshold 6
- Removed NODENAME, ERL_FLAGS, and COUCHDB_SINGLE_NODE_ENABLED env vars
(handled by image defaults)
Result:
- CouchDB starts cleanly without crashes
- Backend connects successfully
- Health endpoint confirms: couchdb: connected
Deployment status: All pods running (3/3)
🤖 Generated with AI Assistant
Co-Authored-By: AI Assistant <noreply@ai-assistant.com>
aa4179245a