Closed jtaleric closed 5 months ago
@jtaleric @krishvoor we are planning to use this operator for our RH OCP v4.14 cluster performance test. But since you mentioned no longer maintained i am afraid we should look for another tool/operator. Could you please guide me for another operator/tool i can use for performance test? I came across kubestone. Mainly planning to test for [Network performance] [Disk performance] [HTTP performance] [Kubernetes resources performance]
Hi @a-thorat, we have
[Network performance]
k8s-netperf will help you with East-West Network Testing
[Kubernetes resources performance]
kube-burner is a performance and scale test orchestration toolset. Kube-burner will help you perform some of these:
Create, delete, read, and patch Kubernetes resources at scale.
Prometheus metric collection and indexing.
Measurements.
Alerting.
[HTTP Performance]
If you are looking for a workload with benchmark termination as HTTP, edge, reencrypt & passthrough you can take a look at ingress-perf
[Disk performance]
For now, you can make use of fio for disk performance.
@krishvoor @jtaleric Thank you for your response. Surely, will explore provided directions and check how good fit with our env. Thank you and Appreciate your help.
As you mentioned for [Disk performance] For now, you can make use of fio for disk performance.
But for the CR , i still need to get benchmark-operator installed on cluster to avail CRD. I am not seeing other way of installation of configuration of FIO or may be i missed reading some more doc. Apologies if i missed. As this operator is set for archive not sure how long will be around and how long we can make use of this FIO CR.
@krishvoor @jtaleric Thank you for your response. Surely, will explore provided directions and check how good fit with our env. Thank you and Appreciate your help.
As you mentioned for [Disk performance] For now, you can make use of fio for disk performance.
But for the CR , i still need to get benchmark-operator installed on cluster to avail CRD. I am not seeing other way of installation of configuration of FIO or may be i missed reading some more doc. Apologies if i missed. As this operator is set for archive not sure how long will be around and how long we can make use of this FIO CR.
There are a couple of teams still using and needing benchmark-operator... I will close this for now, as we won't be archiving benchmark-operator for now. I recently updated the repo to address CNV issues and updated to the latest operator-sdk.
benchmark-operator is no longer being maintained or used within Red Hat.
I am proposing we move the repo to a public archive.