Tags: kube-burner/kube-burner
Tags
Fix : validate QPS and Burst to prevent panic and improve logging (#896) ## Description This change ensures the application handles these situations gracefully. --- ### Before (example failure cases) **Case: QPS invalid → panic**  **Case: QPS valid, Burst negative → panic**  --- ### After (example with fix applied) **No panic, invalid values are corrected at runtime**  Signed-off-by: Ritish134 <ritishnew@gmail>
feat(build): add security hardening flags to binary releases (#880) ## Type of change <!-- Choose a type of change --> - Optimization ## Description <!--- Describe your changes in detail --> pre-built binaries in official releases were missing security hardening features, resulting in package warnings during installation and reduced security posture for end users. this commit adds partial security hardening that's compatible with cross-platform builds: - Add `-s -w` ldflags for symbol and DWARF stripping - Add `-trimpath` to remove file system paths from binaries these improvements apply to all platforms (Linux, Windows, macOS) without requiring CGO, providing better security while maintaining build compatibility. full hardening features like RELRO and PIE require CGO and platform-specific toolchains, which would complicate the release process. users requiring these features can build from source with CGO enabled for now. Component: build ## Related Tickets & Documents - Related #851 Signed-off-by: Josephine Pfeiffer <hi@josie.lol>
Public methods (#875) ## Type of change ## Description These methods must be public so they can be used in external measurements implementations, ## Related Tickets & Documents - Related Issue # - Closes # --------- Signed-off-by: Raul Sevilla <rsevilla@redhat.com>
MetricsCollectionEndpoint config to control metrics end timing (#852) This introduces a new job configuration option `MetricsCollectionEndpoint` to define when the metrics collection should stop. The option supports three values: - AfterJob: collect metrics after the job completes - AfterJobPause: collect metrics after the jobPause duration ends - AfterMeasurements: collect metrics after all measurements are finished This gives users fine-grained control over when to end metrics collection, based on their workload requirements: 1. Users who want to monitor idle periods post resource creation can use AfterJobPause to include the pause in metrics. 2. UDN jobs may want metrics collected immediately after the job, before the pause begins. 3. BGP workloads, which perform route import/export during measurements, benefit from collecting metrics until AfterMeasurements completes. Closes: #846 --------- Signed-off-by: venkataanil <vkommadi@redhat.com>
Add support for monitoring VolumeSnapshot latency (#833) ## Type of change - New feature - Optimization - Documentation - CI ## Description Add support for VolumeSnapshot Latency Generalize the creation of K8S client with additional GroupVersion Use a generic waiter configuration when waiting only based on conditions Add kind specific waiter for VolumeSnapshot and DataVolume condition waiters Disregard condition timestamp if time was not provided Update dependencies Add to test Add to docs Signed-off-by: Ygal Blum <ygal.blum@gmail.com>
Allow changing the content of the objects stored in the objects array (… …#824) ## Type of change - Optimization ## Description Change objects array to hold pointers and pass by pointer Remove duplicate kind field in object struct Fix data volume latency test Signed-off-by: Ygal Blum <ygal.blum@gmail.com>
Ship grafana dashboard in CI (#817) ## Type of change - New feature - CI ## Description Adding a option to ship grafana dashboards in our CI. ## Related Tickets & Documents Closes # #433 ## Testing Tested in local using `DEPLOY_GRAFANA=true make test-k8s`  Signed-off-by: Vishnu Challa <vchalla@vchalla-thinkpadp1gen2.rmtusnc.csb> Co-authored-by: Vishnu Challa <vchalla@vchalla-thinkpadp1gen2.rmtusnc.csb>
PreviousNext