Overview
A mismatch between Kubernetes secrets and PostgreSQL database passwords can disrupt services and hinder access to essential CircleCI features. This issue often arises when Kubernetes secrets are not synchronized with the database passwords used by various services. Understanding the correct setup and how to address mismatches is crucial for maintaining smooth operations.
Prerequisites
Access to your Kubernetes cluster and the ability to update secrets.
Familiarity with Helm for managing Kubernetes applications.
Administrative access to your PostgreSQL database.
Solution
Identify the Mismatch: Determine which services have a password mismatch between the Kubernetes secrets and the PostgreSQL database.
Revert Changes: If you have updated the database password to match the Kubernetes secret, consider reverting this change. Instead, update the Kubernetes secret to match the original database password.
Monitor Services: Ensure that all services are running smoothly after the changes. Check the CircleCI page and other services like Dashboard and Organization Settings for any loading issues.
Verify Correct Setup: Each service should have a unique database user and password. This setup is intentional and correct. When CircleCI Server is installed, a password is assigned to the admin PostgreSQL user and stored in the PostgreSQL secret. Each service uses this admin user and password to create its own database, user, and password.