Organizations that want to install EmpowerID locally can leverage EmpowerID’s DevOps resources to lessen the footprint associated with a full on-premise installation. To facilitate this, EmpowerID provides Docker images of the product in Docker containers. Each container is fully functional instance of EmpowerID that can be easily deployed as a standalone container on a single desktop or as an orchestrated set using Kubernetes. When you opt for this approach, you are ensured to have immediate access to the latest versions of EmpowerID and can go back to a previous version at any time by pulling the appropriate image.
Similarities and Differences
EmpowerID DevOps provides organizations with the full EmpowerID experience, but differs in how the product is delivered. Instead of an MSI that needs to be installed on servers or accessing the platform via the cloud, EmpowerID DevOps delivers the product to you as containers running on “nodes.”
Advantages of the DevOps Approach
The DevOps approach to EmpowerID provides many advantages over on-premise installations to include the following:
Multiple installation options available
Fully managed SaaS from EmpowerID
Can be hosted in AKS, Openshift, etc., cloud Kubernetes platforms that are easily deployed and managed
Can be deployed in an on-premise cluster
Easier patching without interruption to users; the product is delivered as one component (“image”) versus installing and patching files
Ability to scale up or down; there is no need to install anything on nodes
Ability to auto-scale on demand
Provides for better use of resources, by running more components across hardware (vs more hardware for each component)
A possible disadvantage is for enterprise deployment a container orchestrator / cluster is required.
Requirements
To run EmpowerID images, the following requirements must be met:
Container orchestrator / cluster WITH WINDOWS NODE SUPORT | |
---|---|
|
|
Linux Node Requirements | Kubernetes standards |
Logging |
|
SQL Requirements | |
---|---|
|
|
Aggressive Enterprise Disk Subsystem |
|
Memory | 64 GB required, more recommended based on usage scenario. |
Hard Drive Space | Each SQL server should follow Microsoft’s best practice design, utilizing different disk spindles for OS, Logs, Data, and backups. At a minimum, EmpowerID needs the log drive and data drive to have the below available space. Depending on the number of objects in your environment, disk space needs may be significantly higher.
|
Provided by EmpowerID
Container Images
Deployment Templates
Database