As a outcome of NETOBSERV-1770, there's an agreement to the proposed solution where we want to:

1. Run ingress-perf in parallel with node-density-heavy and cluster-density-v2 workload.
2. Enable kube-burner-ocp CHURN option https://kube-burner.github.io/kube-burner/latest/reference/configuration/#churning-jobs 
   1. Currently this only supported via CLI for cluster-density-v2 workload.
   2. For node-density-heavy there's a PR raised: https://github.com/kube-burner/kube-burner-ocp/pull/93 
3. Discontinue 65 nodes ingress-perf scenario.

Done criteria for this story is only #1 in above.