-
Notifications
You must be signed in to change notification settings - Fork 17
Helm Chart for 5.0.5 #24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
9e68c3d to
50a2e12
Compare
Changes in this release: - Converted bandwidth Pod to Job for one-time test execution - Converted latency Pod to Job with post-install hook for automated testing - Updated Chart version to 5.0.5 - Enhanced StatefulSet configuration with improved resource management - Added new configuration options in values.yaml for test parameters - Fixed service port configuration to use integer type These changes provide better Kubernetes-native handling of test workloads, ensuring proper completion tracking and automatic cleanup of finished tests.
50a2e12 to
c9d1ab9
Compare
|
PS: I do not have any knowledge of this tool, so static review only. You may also want to take a look at https://github.com/miniohq/aistor-operator/pull/1081 for improving Helm chart documentation. |
Thank you, impprove documentation can be done in another PR, now I am just updating the helm chart that was still on version 4.0.5 I needed to performance test a cluster. |
… when latency is enabled
If the test fails because the hperf servers were not ready before the Job started, we should allow the container test to be recreated.
By binding the actual pod IP and not the `0.0.0.0` interface we can get mode detailed results of test
Helm chart 5.0.5
Changes in this release:
These changes provide better Kubernetes-native handling of test workloads,
ensuring proper completion tracking and automatic cleanup of finished tests.