As K6 is connected with GitLab, I have a Premium account there. The K6 plan must still be purchased?, and it would be helpful to know how many VU users and machines are supported.
Welcome to the community forum
Good to hear you plan to user k6 connected to GitLab We have several ways to run:
k6 runruns a test locally on the CI server, so you would not need a k6 cloud plan. Explained under the section Configure GitLab CI#configure-gitlab-ci-1.
loadtest-local: image: name: grafana/k6:latest entrypoint: [''] stage: loadtest-local script: - echo "executing local k6 in k6 container..." - k6 run ./loadtests/performance-test.js
k6 cloudruns a test on the k6 Cloud and will probably require a paid plan if the trial is not enough. Configuration described under the section Running k6 Cloud tests.
loadtest-cloud: image: name: grafana/k6:latest entrypoint: [''] stage: loadtest-cloud script: - echo "executing cloud k6 in k6 container..." - k6 cloud ./loadtests/performance-test.js
For cloud you can check the k6 cloud documentation and there is a FAQ section that can help you with subscription questions. Let us know if you still have doubts and I would connect you to someone who can better help.
When running locally (first option above), you could also send the results to the cloud. And in that case you would be using some of the VUh (VU per hour) credits. The difference is explained in the section streaming results vs running on cloud servers.
I hope this helps
Thank you for the feedback. I was curious if I needed to subscribe to the cloud plan for K6 if I wanted to perform a load test utilizing more than 1K VUs, or if GitLab Premium account holders would be able to use it for free.
You would need to subscribe to a k6 plan if you wanted to use more than what the trial allows (you can always start with the trial). GitLab Premium will not allow you to use k6 for free apart from the trial.
You can check the options in Plan & Pricing | k6 Cloud, and you can always contact the team for a personalized plan or e-mail firstname.lastname@example.org.
I hope this helps.