Governance Service Operations
Operators should monitor pod readiness, service health, database migrations, storage access, and Auth Service connectivity.
Health
Section titled “Health”Use Kubernetes readiness and liveness state as the primary operational signal. If HTTP health endpoints fail, inspect service logs, database connectivity, and required secret configuration.
Migrations
Section titled “Migrations”Governance Service has SQL migrations. For customer releases, migration behavior must match the chart values and release notes. Always back up PostgreSQL before upgrading.
Storage
Section titled “Storage”Attachment storage failures usually indicate missing provider credentials,
bucket or container permission issues, or an incorrect storage provider value.
For customer environments, use gcs, azure_blob, or aws_s3; mock storage is
for development and test use only.
Auth Dependency
Section titled “Auth Dependency”Authorization errors can be caused by expired credentials, Auth Service connectivity issues, mismatched API secrets, or missing project membership.