This document discusses the steps for installing PingIntelligence for APIs in Kubernetes cluster.
PingIntelligence ships an example yml
file with its Docker toolkit package. You can use this example yml
file
to deploy PingIntelligence for APIs in a Kubernetes cluster.
The example yml
file creates the following resources in the Kubernetes
cluster:
- 4 statefulsets with one container each for MongoDB, ABS AI engine, ASE, and PingIntelligence Dashboard.
- 3 external services (LoadBalancer type) - One each for ABS AI engine, ASE, and PingIntelligence Dashboard.
- 3 internal services (clusterIP type) - One each for MongoDB, ABS AI engine and ASE
Deploying PingIntelligence PoC using Amazon EKS
This section discusses installing PingIntelligence PoC on Kubernetes cluster node using Amazon EKS.
Deploying PingIntelligence PoC using AKS
This section discusses installing PingIntelligence PoC on Kubernetes cluster node using Azure Kubernetes Service(AKS).
To deploy PingIntelligence PoC:
- Create an AKS cluster. Refer to Quickstart: Deploy an Azure Kubernetes Service (AKS) cluster using the Azure portal, for detailed steps.
- Follow the steps in Deploying PingIntelligence in Kubernetes cluster, and deploy the PingIntelligence PoC on Kubernetes cluster created in step-1.
Deploying PingIntelligence in Kubernetes cluster
Complete the following steps to deploy PingIntelligence in a Kubernetes cluster:
# kubectl get pod -n pingidentity
NAME READY STATUS RESTARTS AGE
abs-0 1/1 Running 0 139m
ase-0 1/1 Running 0 25m
mongo-0 1/1 Running 1 139m
startup-script-5d5d6 1/1 Running 0 119m
dashboard-0 1/1 Running 1 139m
# kubectl get svc -n pingidentity
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
abs-external-service LoadBalancer 10.0.64.46 52.151.201.34 8080:31202/TCP 18h
abs-internal-service ClusterIP None <none> 8080/TCP 18h
ase-external-service LoadBalancer 10.0.27.211 52.151.203.229 80:30677/TCP,443:30396/TCP 18h
ase-internal-service ClusterIP None <none> 8020/TCP,8010/TCP 18h
dashboard-external-service LoadBalancer 10.0.121.85 52.151.204.1 443:31328/TCP 18h
mongo-internal-service ClusterIP None <none> 27017/TCP 18h
If you are deploying in the sideband mode, take the NodePort IP address of ASE to use in API gateway integration.