Skip to content

add subPath to volumeMount postgres-data#367

Open
xring wants to merge 1 commit intoiflytek:mainfrom
xring:fix-postgres-init-fail
Open

add subPath to volumeMount postgres-data#367
xring wants to merge 1 commit intoiflytek:mainfrom
xring:fix-postgres-init-fail

Conversation

@xring
Copy link
Copy Markdown

@xring xring commented Apr 30, 2026

Summary

  • What changed?

add subPath to postgres-data volumeMount

  • Why is this needed?

Full Deployment (with PostgreSQL + Redis) may fail because of lost+found:

The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.

The database cluster will be initialized with locale "en_US.utf8".
The default database encoding has accordingly been set to "UTF8".
The default text search configuration will be set to "english".

Data page checksums are disabled.

initdb: error: directory "/var/lib/postgresql/data" exists but is not empty
initdb: detail: It contains a lost+found directory, perhaps due to it being a mount point.
initdb: hint: Using a mount point directly as the data directory is not recommended.
Create a subdirectory under the mount point.

Validation

  • Backend tests passed
  • Frontend typecheck/build passed
  • OpenAPI SDK regenerated or checked when API contracts changed
  • Smoke test run when relevant

Commands run:

kubectl apply -k deploy/k8s/overlays/with-infra/

Risk

  • User-facing impact:
  • Deployment or migration impact:
  • Rollback approach:

Notes

  • Related issue:
  • Follow-up work:
  • Docs or operator runbooks updated when behavior changed:

@CLAassistant
Copy link
Copy Markdown

CLAassistant commented Apr 30, 2026

CLA assistant check
All committers have signed the CLA.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants