Kubernetes-native load testing platform

Kubeblast

Kubeblast turns your Kubernetes cluster into a Load Testing platform, where running JMeter load tests is simple and efficient.

No scripting, no setup — just run your tests and get results!

✨ Features

• Simplicity First – Just upload your JMX file and click Start. That's it.
• Intuitive UI – Manage jobs, view logs, and monitor execution in real-time.
• Placement Control – Define which Kubernetes nodes to run workloads.
• Resource Control – Set up requests and limits to fit your resource pool.
• Storage Backends – Support for S3 (AWS, MinIO) and PVC.

⭐ Pro Features

Kubeblast Pro unlocks advanced features:

• Built-in RBAC – Role-based access control with support for Users, Admins, and Moderators.
• Moderation Workflow – Assign moderators to review and approve JMX test plans before execution.
• LDAP Support – Integrate with LDAP for centralized authentication and access management.

To request access to the Pro edition, contact me at teymur_gahramanov@outlook.com or via Telegram.

▶️ Quick start

1. Add Helm repository

   helm repo add teymurgahramanov https://teymurgahramanov.github.io/charts && helm repo update teymurgahramanov

2. Install Helm chart

   helm upgrade --install kubeblast teymurgahramanov/kubeblast \
      --set mongodb.enabled=true \
      --namespace kubeblast \
      --create-namespace 
   

3. Access UI on http://localhost:8080 using username admin and password admin. You can use test.jmx for testing.

   kubectl -n kubeblast port-forward svc/kubeblast 8080:80
   

❓ Why Kubeblast?

Unlike YAML-heavy or SaaS-oriented alternatives, Kubeblast delivers a click-and-run experience for existing JMeter (.jmx) scripts, adds RBAC with optional moderator review, is flexible, open-source, and has the lightest footprint.

💡 Example Use-Cases

1. Self-Service Load Testing for QA & Developers

• Problem – Engineers keep pinging DevOps to spin up JMeter or, worse, run tests manually on their laptops.
• Solution – Kubeblast’s Web UI lets users upload a JMX file, launch a test with a few clicks, watch execution logs, and get the report.

2. Team-Wide Resource Sharing

• Problem – Classic load-testing setups spin up extra VM fleets—or overwork developers’ laptops.
• Solution – Kubeblast enables you to share your existing cluster resources with your team.

3. Using Spare Cluster Capacity

• Problem – You need to stress-test at scale but want to use existing resources and not to pay for extra.
• Solution – Beside placement and resource control Kubeblast supports priority class configuration, allowing load tests to use idle cluster capacity — without impacting primary workloads.

4. Load Test Scenario Moderation

• Problem – An unchecked Load Test scenario can flood production, exhausts quotas or accidently (or intentionally) disrupt other workloads.
• Solution – With Kubeblast you can assign “moderator” roles and every new test plan will be reviewed before approving the run.

⚙️ Configuration

All parameters are configurable via environment variables. You can define them directly using Helm values or store in a Kubernetes Secret.

Below is the list of supported environment variables:

Environment Variable	Type	Description	Default Value	Example
PRO_LICENSE_KEY	string	License key for enabling Pro features
PRO_LICENSE_ID	string	License ID for enabling Pro features
LOG_LEVEL	string	Logging level	INFO	DEBUG, INFO, WARNING, ERROR
SECRET_KEY	string	Secret key for JWT tokens and encryption	Random string	your-secret-key
PER_USER_CURRENT_JOBS_LIMIT	int	Maximum number of current jobs per user	3
MONGO_HOST	string	MongoDB host address	localhost
MONGO_PORT	int	MongoDB port number	27017
MONGO_DB_USER	string	MongoDB username	kubeblast
MONGO_DB_PASS	string	MongoDB password	kubeblast
MONGO_DB_NAME	string	MongoDB database name	kubeblast
STORAGE_BACKEND	string	Storage backend type	fs	fs, s3
S3_URL	string	Endpoint URL of S3 compatible storage	-
S3_ACCESS_KEY	string	S3 access key	-
S3_SECRET_KEY	string	S3 secret key	-
S3_REGION	string	S3 region (If required)	us-east-1
S3_BUCKET	string	S3 bucket name	-
K8S_JOB_PRIORITY_CLASS	string	Kubernetes priority class for job pods	-
K8S_JOB_IMAGE	string	JMeter Docker image for load testing	alpine/jmeter:5.6
K8S_JOB_HELPER_IMAGE_S3	string	Helper image for S3 operations	amazon/aws-cli:2.27.12
K8S_JOB_HELPER_IMAGE_FS	string	Helper image for filesystem operations	alpine:3.18
K8S_JOB_IMAGE_PULL_POLICY	string	Image pull policy for Kubernetes jobs	IfNotPresent	Always, Never
K8S_JOB_IMAGE_PULL_SECRETS	JSON	Image pull secrets (JSON array)	[]	[{"name": "regcred"}]
K8S_JOB_NODE_SELECTOR	JSON	Node selector for job placement (JSON)	{}	{"nodeType": "worker"}
K8S_JOB_TOLERATIONS	JSON	Tolerations for job scheduling (JSON array)	[]	[{"key": "dedicated", "operator": "Equal", "value": "loadtest", "effect": "NoSchedule"}]
K8S_JOB_RESOURCES	JSON	Resource requests/limits (JSON)	{}	{"requests": {"cpu": "500m", "memory": "1Gi"}, "limits": {"cpu": "2", "memory": "4Gi"}}
LDAP_ENABLED	bool	Enable LDAP authentication	false
LDAP_SERVER	string	LDAP server address	-	ldap://ldap.example.com:389
LDAP_BASE_DN	string	LDAP base distinguished name	-	DC=example,DC=com
LDAP_BIND_DN	string	LDAP bind distinguished name	-	CN=admin,DC=example,DC=com
LDAP_BIND_PASSWORD	string	LDAP bind password	-
LDAP_USER_SEARCH_FILTER	string	LDAP user search filter	(&(objectClass=person)(sAMAccountName={username}))	(&(objectClass=user)(uid={username}))
LDAP_GROUP_SEARCH_FILTER	string	LDAP group search filter	(&(objectClass=group)(member={dn}))	(&(objectClass=groupOfNames)(member={dn}))
LDAP_USER_ATTRIBUTES	string	Comma-separated user attributes	uid,sAMAccountName,cn,mail,memberOf	uid,cn,mail,displayName
LDAP_GROUP_ATTRIBUTES	string	Comma-separated group attributes	cn,member	cn,memberUid
LDAP_USE_TLS	bool	Use TLS for LDAP connection	false
LDAP_VERIFY_CERT	bool	Verify LDAP server certificate	false

🤝 Contributing

All ideas, issues, and pull requests are welcome!