DEV Community

DarkEdges
DarkEdges

Posted on

Deploying Ping Authorize into Kubernetes

#ping #kubernetes

Deploy pingctl

This enables us to create the necessary secrets needed to enable Ping Licenses for the deployment.

curl -sL https://bit.ly/pingctl-install | sh
sudo mv /home/nirving/pingctl /usr/local/bin/.
Enter fullscreen mode Exit fullscreen mode

The following enables the creation of the secrets

pingctl k8s generate devops-secret > devops.yaml
Enter fullscreen mode Exit fullscreen mode

Add Ping DevOps 

helm repo add pingidentity https://helm.pingidentity.com/ 
help repo update
Enter fullscreen mode Exit fullscreen mode

Create an updated Ingress file 

global:
  envs:
    PING_IDENTITY_ACCEPT_EULA: "YES"
  ingress:
    enabled: true
    annotations:
      nginx.ingress.kubernetes.io/backend-protocol: "HTTPS"
      cert-manager.io/cluster-issuer: vault-issuer
    spec:
      ingressClassName: nginx
pingauthorize:
  ingress:
    hosts:
      - host: pingauthorize.pingauthorize.internal.darkedges.com.au
        paths:
          - path: /
            pathType: Prefix
            backend:
              serviceName: https
    tls:
      - secretName: pingauthorize
        hosts:
          - pingauthorize.pingauthorize.internal.darkedges.com.au
pingauthorizepap:
  ingress:
    hosts:
      - host: pingauthorizepap.pingauthorize.internal.darkedges.com.au
        paths:
          - path: /
            pathType: Prefix
            backend:
              serviceName: https
    tls:
      - secretName: pingauthorizepap
        hosts:
          - pingauthorizepap.pingauthorize.internal.darkedges.com.au
pingdataconsole:
  ingress:
    hosts:
      - host: pingdataconsole.pingauthorize.internal.darkedges.com.au
        paths:
          - path: /
            pathType: Prefix
            backend:
              serviceName: https
    tls:
      - secretName: pingdataconsole
        hosts:
          - pingdataconsole.pingauthorize.internal.darkedges.com.au
pingdirectory:
  ingress:
    hosts:
      - host: pingdirectory.pingauthorize.internal.darkedges.com.au
        paths:
          - path: /
            pathType: Prefix
            backend:
              serviceName: https
    tls:
      - secretName: pingdirectory
        hosts:
          - pingdirectory.pingauthorize.internal.darkedges.com.au
Enter fullscreen mode Exit fullscreen mode

Deploy Ping Authorize 

kubectl apply -f devops.yaml
helm upgrade --install pingauthorize pingidentity/ping-devops --create-namespace --namespace ping -f https://raw.githubusercontent.com/pingidentity/pingidentity-devops-getting-started/master/30-helm/pingauthorize-pingdirectory.yaml -f ingress.yaml
Enter fullscreen mode Exit fullscreen mode

Console

Directory

https://pingdataconsole.pingauthorize.internal.darkedges.com/

Server Username Password
pingauthorize-pingdirectory administrator 2FederateM0re

Policy Editor

https://pingauthorizepap.pingauthorize.internal.darkedges.com/login

username password
admin password123

Top comments (0)

Read next

chauhoangminhnguyen profile image

Setting Up an EXTERNAL-IP for Local LoadBalancer Service

chauhoangminhnguyen -

narmidm profile image

Introducing k8s-pod-cpu-stressor: Simplify CPU Load Testing in Kubernetes

Md Imran -

carrie_luo1 profile image

Deploying High Availability SafeLine WAF on K3s(Part 2)

Carrie -

carrie_luo1 profile image

Deploying High Availability SafeLine WAF on K3s(Part 3)

Carrie -