-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add separate PVC for wal #43
base: v0.7.0-dev
Are you sure you want to change the base?
Conversation
Define WalPvc filed with the name of the pvc and the volume specifications to create a separate pvc for wal files.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To ensure that the Containers moving already existing wal-files, we need informations about the old wal-dir-path.
For example, on an existing cluster you modify the manifest to add an additional wal_dir.
old-wal-dir-ENV can be empty
New wal-Dir-ENV ,map to new volume
If you remove the additional wal-volume from a cluster
old-wal-dir-ENV map to the volume
New wal-Dir-ENV , can be empty
We can use this ENVs on the Container-Project to allow complete customized wal-path.
User provides only the volume specifics for the PVC. The name of the volume is pre-configured as walpvc-cluster-name. The volume is mounted at constants.PostgresPVCWalMount.
When using separate PVc for wal, USE_WAL_PVC is set otherwise False. Use the path in PVCWALDIR for moving wal only when USE_WAL_PVC is set.
Define WalPvc filed with the name of the pvc and the volume specifications to create a separate pvc for wal files.