v0.0.10
⚠️ Breaking Changes
As was mentioned in v0.0.10rc3, since PR #247 all images are built as part of k6-operator Github package.
The old images and releases continue to be available as part of operator package. But it is highly recommended to re-deploy with the new, k6-operator package image, in order to receive the latest updates and releases.
✨ New Features
Watch namespaces are now configurable. Thanks, @dkhachyan!
Readiness and liveness probes can be configured as part of K6 spec, since #230. Thanks, @0xF0D0!
Cloud output in k6-operator is now more performant thanks to metrics aggregation options, added in #229. Additionally, default name of test runs in cloud output has become consistent with other k6 Cloud test runs in #248.
The long-awaited init containers are supported by k6-operator now 🎉 Thanks to @ivanape and @andrei-trandafir! PR #184 and #249. See examples here and here.
A new CRD named PrivateLoadZone has been added in #238 and #239. It is a feature for k6 Cloud users as well as a new type of test run in k6-operator.
Last but not least, k6-operator has been equipped with bundle.yaml to support a simpler method of installation with kubectl apply in #257. See the relevant docs for details.
🐛 Bugs
A bug with nonexistent folder was fixed in #243. Thanks, @vukor!
There was also a couple of important fixes of operator-sdk auto generation, in #217. Thanks, @dkhachyan!
🔧 Maintenance
Dependency updates in this release:
Our docs has been seeing more improvements too:
- Syntax and highlighting was imrpoved in #244 and #245. Thanks, @agilgur5!
- Example with extensions update in #246.
- Instructions for bundle installation in #259.
On a related note, our guide for distributed tests has landed in official k6 Docs!
Full Changelog: v0.0.9...v0.0.10
