Top
Enterprise Postgres 18 for Kubernetes Reference

1.2.5 FEPVolume Child Custom Resource Parameters

1.2.5.1 Create Volumes

Volumes for the cluster nodes(pods) are initially created in accordance with the values set in fepChildCrVal’ storage section of the parent FEPCluster CR.

The parent FEPCluster CR creates a child FEPVolume CR with the respective startup values and the relevant controller(FEPColume Controller) takes care of creating the required volumes. After initial FEPCluster create, new volume cannot be added later and storageClass or accessModes can not be changed.
Only size of an initially created volume can be changed if and only if underlying storageClass supports dynamic change of size.

Below is the schema of the FEPVolume CR:

Field

Mandatory

Sub-Field

Default

Description

archivewalVol

No

size

storageClass

accessModes

1Gi

Defaults to platform default if omitted

Defaults to ReadWriteOnce if omitted

Size of the volume,expandable later

SC is only set at start

Access mode is only set at start

Additional details in section 3.2

backupVol

No

size

storageClass

accessModes

2Gi

Defaults to platform default if omitted

Defaults to ReadWriteOnce if omitted

-do-

dataVol

Yes

size

storageClass

accessModes

2Gi

Defaults to platform default if omitted

Defaults to ReadWriteOnce if omitted

-do-

logVol

No

size

storageClass

accessModes

1Gi

Defaults to platform default if omitted

Defaults to ReadWriteOnce if omitted

-do-

tablespaceVol

No

size

storageClass

accessModes

512Mi

Defaults to platform default if omitted

Defaults to ReadWriteOnce if omitted

-do-

walVol

Yes

Size

storageClass

accessModes

1200Mi

Defaults to platform default if omitted

Defaults to ReadWriteOnce if omitted

-do-

1.2.5.2 Delete Volumes

Equivalent Kubernetes command: kubectl delete FEPVolume <cr_name>

This operation will remove all the PVCs and possibly PVs depending on the default reclaimPolicy of the storageclass used per volume.

With right backup and restore integration by customer, they may not need volumes to be persisted.

Note

Do not delete this CR unless the Cluster has been removed.

Example of FEPVolume CR created

apiVersion: fep.fujitsu.io/v1 
kind: FEPVolume
metadata:
  name: new-fep-19n
  namespace: testswatiproject
spec:
  archivewalVol:
    size: 1Gi
  backupVol:
    size: 2Gi
  dataVol:
    size: 2Gi
  logVol:
    size: 1Gi
  tablespaceVol:
    size: 512Mi
  walVol:
    size: 1Gi
  selectedVolList:
  - name: data
  - name: tablespace
  - name: wal
  - name: log
  sysExtraLogging: false