PingIntelligence

PingIntelligence Kubernetes deployment

Install PingIntelligence for APIs in the Kubernetes cluster, Amazon Elastic Kubernetes Service (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

    • API Behavioral Security (ABS) AI engine

    • API Security Enforcer (ASE)

    • API Publish

    • PingIntelligence Dashboard

    • Apache Zookeeper

    • Kafka

  • Six external services (LoadBalancer type), one each for (Configurable to expose):

    • MongoDB

    • ABS AI engine

    • ASE

    • API Publish

    • Zookeeper

    • Kafka

      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

    • API Publish

    • Zookeeper

    • Kafka

PingIntelligence Kubernetes supports RHEL 7.9.

This deployment of PingIntelligence on a Kubernetes cluster node is suitable for Amazon EKS.

The Kubernetes cluster can be configured on the Amazon EKS. You can install PingIntelligence on a Kubernetes cluster node using Amazon EKS.

Deploying PingIntelligence using Amazon EKS

About this task

To deploy PingIntelligence on a Kubernetes cluster node using Amazon EKS:

Steps

  1. Create an Amazon EKS cluster on a RHEL or host.

    You can use either eksctl or AWS command-line interface (CLI) for creating the Kubernetes cluster. Refer to the following links when creating and managing the Kubernetes cluster using Amazon EKS.

    For more information, see the following:

  2. Follow the steps in Deploying PingIntelligence in Kubernetes cluster and deploy PingIntelligence on the Kubernetes cluster that you created in step 1.