Advanced Configurations
Helm Configurations
Following are the service helm charts:
Census Service:
Plan Service:
Resource Generator:
Database and Migration Configuration Overview -
Database Configuration Information
The configuration snippet provides the details required to set up and connect to a database, including environment-specific handling, credentials, schema information, and other related settings. Below is a structured breakdown:
Database Connection Information
DB_URL
health-db-url
or db-url
from egov-config
URL for connecting to the database. Uses health-db-url
in the "health" namespace, else db-url
.
DB_HOST
db-host
from egov-config
Hostname or IP address of the database server.
DB_PORT
"5432"
Port number for database connection (default PostgreSQL port).
DB_NAME
db-name
from egov-config
Name of the database being connected to.
DB_SCHEMA
Namespace value ("health")
for Microplanning or "public"
Specifies the schema within the database. Defaults to "public"
if no namespace is provided.
DB_USER
username
from db
secret
Database username used for authentication.
DB_PASSWORD
password
from db
secret
Database password for authentication.
Flyway Migration Information
FLYWAY_USER
flyway-username
from db
secret
User for running Flyway migrations.
FLYWAY_PASSWORD
flyway-password
from db
secret
Password for Flyway migration user.
FLYWAY_LOCATIONS
flyway-locations
from egov-config
Directory or path for Flyway migration scripts.
SCHEMA_TABLE
schemaTable
from initContainers.dbMigration
Table name for tracking Flyway migrations.
General Notes
ConfigMap and Secrets Integration: Sensitive data like
DB_USER
,DB_PASSWORD
, and Flyway credentials are securely retrieved from Kubernetes secrets (db
secret). Non-sensitive configurations likeDB_HOST
andDB_NAME
are stored in ConfigMaps (egov-config
).Namespace-Specific Configuration: The
DB_URL
andDB_SCHEMA
are tailored for specific namespaces. For example, the "health" namespace uses a dedicatedhealth-db-url
key and the namespace value for the schema.Default Settings: Where applicable, defaults are provided. For instance, the schema defaults to
"public"
and the port defaults to5432
.
These configurations enhance the flexibility and usability of the core services of HCM-Microplanning, ensuring smoother operations and better alignment with user needs.
Last updated