This document discusses the steps for installing PingIntelligence for APIs in the Kubernetes cluster(AWS EKS).
PingIntelligence ships with Helm-Chart that is packaged with the Docker Toolkit, and can be used to deploy PingIntelligence in a Kubernetes cluster.
PingIntelligence creates the following resources in the Kubernetes cluster:
- Seven statefulsets with one container each, for MongoDB, ABS AI engine, ASE, APIPublish, PingIntelligence Dashboard, Apache Zookeeper and Kafka.
- Seven external services (LoadBalancer type), one each for MongoDB, ABS AI engine, ASE,
APIPublish, Zookeeper and Kafka.(Configurable to expose)Note: Each component has an external service of type LoadBalancer, that can be exposed by setting the flag in
values.yaml(expose_external_service: false). By default, this value is true for ASE. The dashboard will always be exposed since it must be accessible externally. - Six internal services (clusterIP type), one each for MongoDB, ABS AI engine, ASE, APIPublish, Zookeeper and Kafka.
PingIntelligence Kubernetes supports RHEL 7.9.
Note: This deployment
of PingIntelligence on a Kubernetes cluster node is suitable for AWS EKS.
The Kubernetes cluster can be configured on the Amazon Elastic Kubernetes Service (EKS). This section describes installing PingIntelligence on a Kubernetes cluster node using Amazon EKS.