β¨ New features
Starting from this release, k6-operator supports multiple PrivateLoadZone
s π As a reminder, previously it was possible to have only one PrivateLoadZone
per installation. Now one can create several in a row and have them all working simultaneously:
$ kubectl -f plz-demo.yaml apply
privateloadzone.k6.io/plz-demo created
$ kubectl -f plz.yaml apply
privateloadzone.k6.io/kung-fu created
$ kubectl get privateloadzones.k6.io -A
NAMESPACE NAME AGE REGISTERED
plz-ns plz-demo 6s True
plz-ns kung-fu 14s True
Note, however, that restriction of 100% distribution remains: it is possible to reference only one PrivateLoadZone
in a k6 test.
The PLZs are distinguished by name only. This is required to be backward compatible with the older PLZs. Since it's backward compatible, there is no migration required: just an update of k6-operator to the latest release should be sufficient to switch to the new setup. The start of the new version of the app will read the registered PLZ in the system and continue to work as before, but now with the potential to add more PLZs if you'd like.
Grafana Cloud k6 sets the maximum number of PLZs per organization. By default, it is 5. If you need more, please contact customer support.
The documentation update will follow next week.
π¦ Helm
There have been quite a few improvements around ServiceMonitor
usage:
- Ability to configure the
ServiceMonitor
withnamespace
,jobLabel
,interval
,scrapeTimeout
,labels
, and some other fields. Thanks, @EladAviczer!β οΈ This is a breaking change: instead ofprometheus.enabled
, configuration now happens viametrics.serviceMonitor.enabled
. Please adjust your Helm values accordingly!
- It is now possible to have k6-operator's
Service
without enablingauthProxy
. To do that, there is aservice.enabled
option. Thanks, @afreyermuth98!
πͺ Maintenance
There were a lot of CI improvements to harden our security stance. One of the most noticeable additions is that Zizmor scanning is executed on each pull request.
Some minor Golang library updates were also done here.
π Documentation
Last but not least, the internal docs now have a write-up about the NDE (Native Distributed Execution) proposal in k6 OSS and its potential impact on k6-operator.
With the help of @heitortsergent, we are improving our troubleshooting docs. The existing guide will be split into two parts (general & TestRun
troubleshooting VS PrivateLoadZone
troubleshooting) and simplified to make them more useful.
Full Changelog: v0.0.20...v0.0.21