Architecture / Concepts

This topic explains the architecture and important concepts of Dynamic Infrastructure.

How does it work?

NeoLoad Web can deploy pods based on your zone and test settings before running the test campaign. Once finished, spun pods will be automatically switched off and destroyed.

Cluster authentication

NeoLoad Web requires a service account to manage a Kubernetes / OpenShift cluster and a service account token to authenticate on this cluster.

This service account should be bound to a role that have these rules (permissions):

rules:
- apiGroups: [ "", "apps", "extensions" ]
  resources: ["deployments", "replicasets"]
  verbs: ["get", "list", "create", "update", "patch", "delete"]
- apiGroups: [ "", "apps", "extensions" ]
  resources: ["pods", "events"]
  verbs: ["get", "list"]      
- apiGroups: [ "" ]
  resources: ["replicationcontrollers"]
  verbs: ["get", "list", "create", "update", "patch", "delete"]

These authorizations can be automatically created with the NeoLoad Web dynamic infrastructure user access helm chart.