EKSCTL_CLUSTER_NAME=eks-heimdall-onprem-cluster
EKSCTL_NODEGROUP_NAME=eks-heimdall-onprem-worker-nodes
EKSCTL_KUBERNETES_VERSION=1.x.x
eksctl create cluster \
--name ${EKSCTL_CLUSTER_NAME} \
--version ${EKSCTL_KUBERNETES_VERSION} \
--region us-west-2 \
--zones us-west-2a,us-west-2b,us-west-2c \
--nodegroup-name ${EKSCTL_NODEGROUP_NAME} \
--node-type t3.2xlarge \
--nodes 4 \
--nodes-min 2 \
--nodes-max 6 \
--ssh-access \
--ssh-public-key ~/.ssh/id_rsa.pub \
--managed \
--vpc-nat-mode Disable

browserMonitoringAgent:
enabled: true
server: "<proxy server address>"
bypassList: "<specify the domain URLs that you want to bypass separated by semicolon>"

For example, bypassList: "*abc.com;*xyz1.com;*xyz2.com" Domain URLs that you specify in bypassList are not redirected to the proxy server. You can add any number of domains in the bypassList. All other unspecified domain URLs are redirected to the proxy server.

# Use the sum-chrome-agent image you just loaded as the base image
FROM appdynamics/chrome-agent-psa:<agent-tag>
USER root
RUN apk add py3-pip
USER appdynamics
# Install algorithm for python3 on top of that
RUN python3 -m pip install algorithms==0.1.4 --break-system-packages

docker build -t sum-chrome-agent:<agent-tag> - < Dockerfile

To create a new namespace for Ignite, enter:

kubectl create namespace measurement

Beforeyou deploy Apache Ignite, you must set some configuration options. To view the configuration options, navigate to the previously downloaded ignite-psa.tgz file and enter:

helm show values ignite-psa.tgz > values-ignite.yaml

persistence:
# To turn on persistence, kindly set enabled to true. Do not modify onPremMode value
enabled: true
onPremMode: true
enableEfs: false  # Set to true if you are using efs
persistenceVolume:
size: 8Gi
provisioner: efs.csi.aws.com # Replace with your provisioner value
provisionerParameters:
type: efs # Specify that it's for Amazon EFS
fileSystemId: fs-01285427ea904c120  # Replace with your EFS file system ID
provisioningMode: efs-ap # Replace with your provisioner mode
walVolume:
size: 8Gi
provisioner: efs.csi.aws.com # Replace with your provisioner value
provisionerParameters:
type: efs  # Specify that it's for Amazon EFS
fileSystemId: fs-01285427ea904c120  # Replace with your EFS file system ID
provisioningMode: efs-ap # Replace with your provisioner mode
enableHostPath: false  # Set to true if you are using hostpath
hostPath:
persistenceMount: /mnt/ignite/persistence
walMount: /mnt/ignite/wal

kubectl get pv -n measurement
kubectl get pvc -n measurement

helm install synth ignite-psa.tgz --values values-ignite.yaml --namespace measurement

kubectl get pods --namespace measurement

Proceed to the next steps only after the Apache Ignite pods run successfully.

Using a single command, you can deploy the Helm chart, which contains the deployment details. To deploy the agent, use the Helm chart sum-psa-heimdall.tgz in the zip file that you downloaded previously. Before you deploy the Private Synthetic Agent, you must set some configuration options. To view the configuration options, navigate to the previously downloaded sum-psa-heimdall.tgz file and enter:

helm show values sum-psa-heimdall.tgz > values.yaml

These are the configuration key-value pairs that you need to edit in the values.yaml file:

# To turn on persistence, kindly set enabled to true
persistence:
enabled: false
storageClass:
provisioner: efs.csi.aws.com # Specify that it's for Amazon EFS
parameters:
type: efs  # Specify that it's for Amazon EFS
fileSystemId: fs-01285427ea904c120   # Replace with your EFS file system ID
provisioningMode: efs-ap  # Replace with your provisioner mode

kubectl get pv -n measurement
kubectl get pvc -n measurement

measurementPodMetadata:
  enableCustomTolerations: false  # Enable use of custom tolerations from this config
  enableCustomAffinity: false     # Enable use of custom affinity rules from this config
  enableCustomLabels: false      # Enable use of custom labels from this config
  automountServiceAccountToken: false # Automatically mount service account token in pods
  labels: # Custom labels to apply to the Pod metadata
    team: "qa"             # Example: assign pod to QA team
    priority: "high"       # Example: set custom priority level
    app.kubernetes.io/managed-by: "scheduler-service"  # Standard label
  tolerations:
    - key: "dedicated"                      # Tolerate nodes tainted with key=dedicated
      operator: "Equal"                     # Match taint value exactly
      value: "measurement"                  # Accept taint with value=measurement
      effect: "NoSchedule"                  # Allow scheduling on such tainted nodes
  affinity:
    nodeAffinity:
      requiredDuringSchedulingIgnoredDuringExecution:
        nodeSelectorTerms:
          - matchExpressions:
              - key: "kubernetes.io/hostname"  # Node must have this hostname
                operator: "In"                 # Match exact value
                values:
                  - "node-1"                   # Only allow node named node-1
      preferredDuringSchedulingIgnoredDuringExecution:
        - weight: 80                           # Strong preference weight
          preference:
            matchExpressions:
              - key: "topology.kubernetes.io/zone"  # Prefer node in this zone
                operator: "In"
                values:
                  - "us-central1-a"
    podAffinity:
      requiredDuringSchedulingIgnoredDuringExecution:
        - labelSelector:
            matchExpressions:
              - key: "app"                     # Co-locate with pod having app=frontend
                operator: "In"
                values:
                  - "frontend"
          topologyKey: "kubernetes.io/hostname"  # Must be on the same node
      preferredDuringSchedulingIgnoredDuringExecution:
        - weight: 50                            # Medium preference
          podAffinityTerm:
            labelSelector:
              matchExpressions:
                - key: "app"                   # Prefer proximity to app=logger pods
                  operator: "In"
                  values:
                    - "logger"
            topologyKey: "topology.kubernetes.io/zone"  # Prefer same zone
    podAntiAffinity:
      requiredDuringSchedulingIgnoredDuringExecution:
        - labelSelector:
            matchExpressions:
              - key: "app"                     # Do NOT schedule with app=backend pods
                operator: "In"
                values:
                  - "backend"
          topologyKey: "kubernetes.io/hostname"  # Must not be on same node
      preferredDuringSchedulingIgnoredDuringExecution:
        - weight: 30                            # Low preference to avoid
          podAffinityTerm:
            labelSelector:
              matchExpressions:
                - key: "env"                   # Prefer to avoid pods in env=production
                  operator: "In"
                  values:
                    - "production"
            topologyKey: "topology.kubernetes.io/region"  # Prefer different region

You can leave the rest of the values set to their defaults or configure them based on your requirements. See Configure Web Monitoring PSA and API Monitoring PSA for details on shepherd URL, credentials, location, and optional key-value pairs.

helm install heimdall-onprem sum-psa-heimdall.tgz --values values.yaml --namespace measurement

All the Kubernetes resources are created in the cluster, and you can use Heimdall. After a few seconds, Heimdall initializes and is visible in the Controller.

kubectl get pods --namespace measurement

To make any changes to values.yaml after the initial deployment, navigate to the previously downloaded sum-psa-heimdall.tgz file and enter:

helm upgrade heimdall-onprem sum-psa-heimdall.tgz --values values.yaml --namespace measurement

helm uninstall heimdall-onprem --namespace measurement

./install_psa -e kubernetes -l -v -u <Shepherd-URL> -a <EUM-account> -k <EUM-key> -c <location-code> -d <location-description> -t <location-name> -s <location-state> -o <location-country> -i <location-latitude> -g <location-longitude> -p <PSA-tag> -r <heimdall-replica-count> -z <agent-type> -m <chrome-agent_min/max-memory> -n <API-agent_min/max-memory> -x <chrome-agent_min/max-CPU> -y <API-agent_min/max-CPU> -b <heimdall_min/max-memory> -f <heimdall_min/max-CPU> -q <ignite-persistence> -w <heimdall_proxy_server>~<api_monitoring_proxy_server>~<web_monitoring_proxy_server> -B <"bypassURL1;bypassURL2;bypassURL3"> -C true -A <serviceaccount-name> -U <userID> -G <groupID> -N <run_as_a_non-root_user> -F <file_system_groupID> -O <override_the_security_context>

A sample installation command looks like this:

./install_psa -e kubernetes -u <Shepherd-URL> -a <EUM-account> -k <EUM-key> -c DEL -d Delhi -t Delhi -s DEL -o India -i 28.70 -g 77.10 -p 23.5 -r 1 -z all -m 100Mi/500Mi -n 100Mi/100Mi -x 0.5/1.5 -y 0.1/0.1 -b 2Gi/2Gi -f 2/2 -q true -w 127.0.0.1:8887~127.0.0.1:8888~127.0.0.1:8889 -B "*abc.com;*xyz1.com;*xyz2.com" -C true -A serviceaccount-name -U 9001 -G 9001 -N true -F 9001 -O true