Skip to content

Latest commit

 

History

History
124 lines (76 loc) · 3.17 KB

example-install-camunda-aws-eks.adoc

File metadata and controls

124 lines (76 loc) · 3.17 KB
Raw

AWS EKS Camunda Install

Table of Contents

Disclaimer

Important
 This document is not intended to create production envronemnt. Rather, it’s a refrence to demonstarte a basic simple install of Camunda Platform on AWS EKS. Also to clarify provide practical architectural guidance for Camunda Optiimze in Kubernetes environments.

Step 1: Provision Cluster

Note
 you can skip this if you have done it already with Camunda-Optimize-HELM and you don’t want a separate cluster for Camunda. So you will be installing into same EKS Cluster.

Otherwise see Provision EKS Cluster to provision a new cluster on EKS. Keep in mind this is just for testing and not intended setup for production.

Step 2: Setup Cluster

Install Postgres

This assumes you will use the postgres image defined in the docs here.

Which is a imaged pulled and configured in the HELM chart.

If you provision another Postgres you will need to change the values.yaml

Install the Database Secret

Install the docker-registry secret

Install AWS Ingress Controller

See the doc here

Step 3: Configure the HELM Charts for Camunda Platform Install

Configure Kubernetes Ingress

Important
 make sure to disable the Nginx Ingress Config 
# Ingress config for AWS EKS ingress controller
elbIngress:
  enabled: true
  annotations: {
    kubernetes.io/ingress.class: alb,
    alb.ingress.kubernetes.io/scheme: internet-facing,
#    alb.ingress.kubernetes.io/target-type: ip,
  }
  hosts:
    path: /*
#  tls: []
#    - secretName: camunda-bpm-platform-tls
#      hosts:
#        - camunda-bpm-platform.local

Change the service

Important
 make sure to change the service.type to NodePort. 
# Using NodePort for AWS EKS Controller
# Use ClusterIP for Nginx Controller
  service:
   type: NodePort
   port: 8080
   portName: http

Step 4: Run the HELM install

helm install workflow-demo ./charts/camunda-bpm-platform/

Get the Endpoint to access Camunda Platform

kubectl get ingress --all-namespaces

The value in the address field is the endpoint for accessing Camunda. If you want a more permanent address configure DNS service.

Troubleshooting

Get the cluster config

eksctl get cluster --name camunda-cluster

Delete stuck pods

kubectl delete pod <PODNAME> --grace-period=0 --force --namespace <NAMESPACE>

Get pods

kubectl get pods

Get logs for pod

kubectl logs -f <pod-name>

Get all services

kubectl get svc --all-namespaces

Get the details of a kubernetes component

kubectl describe <pods, svc, ingress, deploy>

Pretty print more info about pods

kubectl get nodes -o wide |  awk {'print $1" " $2 " " $7'} | column -t