Magnolia PaaS Architecture
A typical Magnolia PaaS deployment contains productive and non-productive cluster(s) with our Magnolia Platform Services providing metrics, logs, alert management, and cluster orchestration. The clusters can be on AWS, Azure, or a mixture of both.
These metrics can be viewed directly via the Cockpit. |
The Docker Registry, pipeline, source control (git), Jira support, cluster orchestration, the CDN, and of course, the Cockpit are all accessible by the customer.
As shown below, users must be authenticated and authorized to access the core elements of Magnolia PaaS, which include:
-
the Cockpit
-
Source control (
git
)
In fact, even the elements themselves require authentication (via Bearer Token) to perform tasks, further securing your Magnolia deployment.
Kubernetes and sidecars
Magnolia PaaS uses Kubernetes for baseline orchestration of its environments. This is an explicit dependency. Helm charts are used to deploy releases on the Kubernetes cluster.
Item | Note | ||
---|---|---|---|
A |
The CDN is deployed between the end user and the Magnolia instances. |
||
B |
Magnolia instances (author/public) are each deployed in a Kubernetes pod containing their own sidecars and K8s workers. |
||
C |
Sidecar containers are deployed to initialize containers before Magnolia CMS starts.
|
||
D |
The K8s workers handle pod availability. |