FEPCluster

Definition

///

Create: kubectl create -f fepcluster.yaml
Delete: kubectl delete fepcluster <clusername>
Update: kubectl apply -f fepcluster.yaml
List: kubectl get fepcluster

FEPCluster CR Example

apiVersion: fep.fujitsu.io/v2 
kind: FEPCluster
metadata:
  name: new-fep
  namespace: new-fep
spec:
  fep:
///
        wuC4
        -----END CERTIFICATE-----

It should also be noted that all the passwords / passphrase and certificates will be masked after the creation of the CR. This includes

• Also, inital pgAdminPassword: admin-password

• pgpassword: mydbpassword

• pgreplpassword: repluserpwd

• tdepassphrase: tde-passphrase

• pgRewindPassword: rewind_passoword (Optional - if defined)

• pgMetricsPassword: metrics_password (Optional - if defined)

• pgSecurityPassword (if defined)

• sslpassphrase under sysTde.tdek.kmsDefinition (if defined)

• certificate.key

• certificate.crt

• certificate.cacrt

Values of child CRs at the time of initial deployment of cluster, are stored in FEPCluster under fepChildCrVals, e.g. for Server certificates, Configuration of FEP, User details.

All fields for FEPCluster CR and its child CRs should be managed through FEPCluster CR only. Operator will reflect the changes to respective child CR to be processed. The fields that not allowed to change will not be reflected from parent to child CR and hence will not have any affect.