- Print
- PDF
An overview of the deployment topology when Knovvu products are deployed on a customer Kubernetes cluster is provided below.
CPU and memory requirements can be found in the Hardware Sizing Document related to the Knovvu Product to be installed.
Kubernetes Cluster Namespaces
Services deployed by Sestek use different namespaces in Kubernetes for resource isolation. Namespace sestek-common exists in all deployments and contains common platform applications such as Nexus, Vault, Jenkins and Elastic Stack. Other namespaces (e.g. sestek-core, sestek-stai, sestek-ca, sestek-cai) are included in deployments in different combinations based on the product that is deployed (e.g. Knovvu Analytics, Knovvu Virtual Agent).
VMs outside Kubernetes Cluster
VM type | Function | OS | Remarks |
---|---|---|---|
Terminal Server | Terminal Server is the server which the Sestek Application Support Engineer connects to in order to bootstrap the installation process. | Windows | |
License Servers | These servers control the consumption of licenses. They run outside the Kubernetes cluster and have a separate installation process from the containerized Knovvu applications. | Windows | |
Database | As relational databases, Knovvu applications work either with Microsoft SQL Server or PostgreSQL. | Installation and management of relational databases are always expected to be handled by the customer. |
Container Registry Configuration
Customers are required to proxy their container registries to the Central Knovvu Container Registry (docker.sestek.com). If this is not possible, then customers should pull all the images from Central Knovvu Container Registry and push them to their container registry. If this is the case, image list will be provided by Sestek.
Next topic: Deployment Procedure