[PMS] Persistent storage of policies and type definitions 50/121050/17
authorPatrikBuhr <patrik.buhr@est.tech>
Fri, 30 Apr 2021 13:12:51 +0000 (15:12 +0200)
committerPatrikBuhr <patrik.buhr@est.tech>
Fri, 11 Jun 2021 06:33:33 +0000 (08:33 +0200)
commit746ff37c26277159584e2ad9b01b55a8f70fbd71
treee70ef861df67289804dcfd757445a552f9ee1f16
parent87411cc03c91a0ba7f26fcd9e7e4bd8afb75b24e
[PMS] Persistent storage of policies and type definitions

Improvements:
 - Using common metadata for the PV and the PVC.
 - Changed the deployment to a stateful set.

Even Deployments with one replica using ReadWriteOnce volume
are not recommended. This is because the default Deployment
strategy creates a second Pod before bringing down the first Pod
on a recreate. The Deployment may fail in deadlock as the
second Pod can't start because the ReadWriteOnce volume is
already in use, and the first Pod won't be removed because
the second Pod has not yet started.
Instead, use a StatefulSet with ReadWriteOnce volumes.

Change-Id: If3477be43eee5348a9142cceb832bbb2bf9d6017
Issue-ID: CCSDK-3256
Signed-off-by: PatrikBuhr <patrik.buhr@est.tech>
kubernetes/a1policymanagement/templates/pv.yaml
kubernetes/a1policymanagement/templates/pvc.yaml [deleted file]
kubernetes/a1policymanagement/templates/statefulset.yaml [moved from kubernetes/a1policymanagement/templates/deployment.yaml with 92% similarity]
kubernetes/a1policymanagement/values.yaml