How neotys-labs/helm-neoload-web works
This repository is a Helm chart for deploying NeoLoad Web to Kubernetes, not the application implementation. The documented deployment includes frontend, backend, backend-utilities, and an optional-by-configuration MCP Server, with external MongoDB and ingress prerequisites. NeoLoad Web provides centralized real-time test visibility, trend graphs, and test-detail analysis, but those application workflows are outside this chart. No source excerpts were supplied, so links between individual Kubernetes resources are not asserted; dashed links mark deployment relationships inferred from the chart’s purpose and documented prerequisites.
Main entry points: Chart.yaml Helm chart · deployment-back.yaml Backend · ingress.yaml Web ingress · deployment-front.yaml Frontend
Components 16
Application workloads
- Frontend
templates/deployment-front.yaml - Backend
templates/deployment-back.yaml - Backend utilities
templates/deployment-backend-utilities.yaml - MCP Server
templates/deployment-mcp-server.yaml
External access
- Web ingress
templates/ingress.yaml - MCP ingress
templates/ingress-mcp-server.yaml - Application services
templates/service.yaml - MCP service
Deployment configuration
- Credentials and keys
templates/secrets-mongo.yaml - Logging configuration
templates/configmap-logger-config.yaml
Cluster platform
- Helm chart
Chart.yaml - Cluster permissions
templates/cluster-role.yaml
Other components
- Cluster operator
- MongoDB
- Kubernetes cluster
- Ingress controller
Connections 10
- Cluster operator → Helm chart: installs or upgrades
README.md - Helm chart → Kubernetes cluster: deploys into
README.md - Helm chart → Frontend: deploys workload
- Helm chart → Backend: deploys workload
- Helm chart → Backend utilities: deploys workload
- Helm chart → MCP Server: deploys workload
- Ingress controller → Web ingress: routes external traffic
README.md - Web ingress → Frontend: routes to app
- MongoDB → Kubernetes cluster: accessible from
README.md - Backend → MongoDB: uses database