Applications can be installed either on-premise or in cloud environment. A minimum cluster environment can be setup using a single virtual machine (VM) for test purposes. However a single-node cluster is not recommended for production.
CPU and Memory
16 vCPU and 16 GB of memory is recommended for test environment. This does not include the CPU and memory requirements of the cluster. For a production use, 32 vCPU and 32 GB of memory is recommended apart from the resources needed to run the cluster.
For a test environment 30 GB of storage is recommended. For production, 1 TB of storage is a good start and it is recommended to use highly-available commercial solutions to store database files and pod data.
The different components of KOBIL Security Server Architecture are explained below:
A load balancer is required to distribute requests to the cluster. A software or hardware solution can be used. For example, an opensource load balancer such as HAProxy or NGiNX can be used for test environment. Commercial solutions are recommended for production environments.
External Load Balancer
These are used to direct external HTTP requests into a cluster. An external load balancer helps in routing internet traffic to specific nodes identified by ports.
The Ingress-Controller functionality is used to route to the appropriate KOBIL Security Server service. There is no need to specify different ports.
KOBIL Security Server
KOBIL Security Server is an optimal central management solution for all your KOBIL authentication clients. The KOBIL product portfolio covers a wide range of security solutions, from One-Time Password (OTP) solutions to Smart Card based solutions through the cutting-edge technology in Two-Factor Authentication (2FA) via Mobile App Security Technology (mAST). You will be able to manage all the devices and the software applications through a central management system, in a secure, mobile and customizable way, without exposing any of your business logic and data to security risks.
A variety of databases are needed to install the applications. In Kubernetes based test environment, each databases can be installed as a “pod” in the cluster. However, it is recommended to use database servers for production.