- Minikube and Kubernetes environment set up
- Creation of basic minikube deployment
- https://severalnines.com/database-blog/using-kubernetes-deploy-postgresql
- Set up postgres server and cps application
- Host IP ?
- Error: Application Failed to start
- Description: The dependencies of some of the beans in the application context form a cycle "notificationService->cpsDataUpdatedEventFactory→cpsDataServiceImpl"
- Ingress
- allows access without IP address
- calls to each pods
- https://avinetworks.com/glossary/kubernetes-load-balancer/
--------
web controller - stateless ---- replica sets
database - stateful
--------
bottleneck — filesystem —database — vertical scaling maybe more CPU/memory -
--- own deployment maybe ?
replicate cps core ncmp while being stateless and replicas - make sure that no state is kept (no cache) — look at all
--- if all user is in same deployment then maybe multiple instance of the database but the synchronisation will be complex (postgres running in clustermode)
can deploy database in clustermode ----
as per bruno - there's no authentication on cps
different database for different dataspaces ?
-----------------------------
Load Balancing
| Gliffy Diagram | ||||||
|---|---|---|---|---|---|---|
|
Horizontal Pod Autoscaler (HPA) and Vertical Pod Autoscaler (VPA)
https://www.heydari.be/papers/WoC-stef.pdf
- Scaling stateful applications requires more planning and is thus also slower in most cases. This makes vertical scaling the preferred method of scaling for stateful applications during a load peak, as no new replicas need to be scheduled.