rakutentech / shibuya

rakutentech/shibuya Issues

Local env along with colima doesn't work with macos v14 (Sonoma)
Updated 3 months ago4
Test with Java 21 and Jmeter
Closed 10 months ago4
HTTP2 Support at Jmeter engines
Updated 4 months ago
Shibuya Dockerfile to be completely configuration neutral
Closed 4 months ago1
A new Release pipeline
Closed 6 months ago1
Shibuya distributed mode
Updated 6 months ago2
Documentation at Metrics side
Updated a year ago
Reduce the load to k8s API server side
Closed 2 years ago2
New Ingress controller issues
Closed 2 years ago1
Currently cannot run unit tests locally
Updated 2 years ago
Make duration from minutes to seconds
Closed 2 years ago3
During a large collection(>300 engines) is being launched, we could see 504 errors at Load balancers
Closed 2 years ago
Showing available resources in non on-demand cluster
Updated 2 years ago
Wrong error message when the engine service is deleted
Updated 2 years ago
Engine auto deletion time goes to negative value
Updated 2 years ago1
Upgrade Shibuya k8s api versions
Closed 2 years ago1
Add engines cap when user is uploading the plan
Closed 3 years ago1
Engine lifespan counter
Closed 3 years ago
More details about shibuya engine status
Closed 3 years ago
Make Shibuya be useable without any yamls/jmx
Updated 4 years ago
Multiple collections cannot scale in/out when used concurrently
Closed 4 years ago6
Dedicated k8s for project
Closed 4 years ago1
Implement missing APIs
Updated 4 years ago
Cannot use large files with high number of engines
Closed 4 years ago7
Do not reset request, status, latency count during release
Updated 4 years ago1
Purge could take long time
Closed 4 years ago1