OpenShift4-tools
OpenShift4-tools copied to clipboard
RobertKrawitz
OpenShift 4 tools
Support cluster ingress/egress traffic via external uperf server(s).
Network datapaths typically handle packets in two different ways: - When it's a new "flow", identified by it's 5-tuple (src/dst MAC, src/dst IP, L4 port), datapaths typically need extra processing,...
This would enable collecting data in addition to what Prometheus collects, and also collect it at a finer granularity (Prometheus metrics are at 30-second granularity; Pbench collects some data at...
Clsuterbuster should store the benchmark results and other relevant metadata in the in-cluster Prometheus database so that all benchmark results and system metrics are available in one single database. The...
Clusterbuster normally creates one or more workload workspaces and a sync workspace with names prefixed with the base name. It should be possible to optionally run all components within one...
Clusterbuster does not currently support OSV.
Depending on the configuration, different types of stressors might end up competing for the same resources. For example, if PAO (Performance Add-on Operator) is used on a cluster, kubelet and...
Hi, Concerning the clusterbuster tool, the --node_selector option apparently only supports node labels which have an empty value. It would be nice to be able to use node labels with...
`oc exec` does not work on privileged pods unless the user is logged in as a privileged user. Consider using `oc rsh` to avoid this. @gqlo