| Scroll ignore | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||
There are 2 options for deploying the K platform: 1) SaaS; or 2) Your Cloud
...
This can include OpenShift, AWS’s Elastic Kubernetes Service (EKS), Azure Kubernetes Services (AKS) and Google Kubernetes Engine (GKE).
See this guide Deploying to your own Kubernetes Service to deploy K locally.
The following diagram outlines how K is deployed in a typical Enterprise environment.
...
Kubernetes Service
Components | Details |
Nodes | K is deployed across a number of nodes (minimum of 4 nodes). Each node requires a minimum of 4 vCPU and 16gb Memory. Contact the KADA team to work through the right sizing for your data ecosystem. Example specifications for cloud services include:
|
Object store | A location for landing files from data sources and data tools before processing by K. This location must be accessible by the Kubernetes Service. The typical size for the Object store is 200Gb but may need to expand depending on your data retention needs. |
Other Components
Components | Details |
KADA Repository | Your Image Registry connects to the KADA repository hosted externally (internet access required) to deploy and update the K platform. This approach enables you to quickly and easily download the K updates. |
...