Describe the solution you'd like
Add churn to web-burner workload.
There are two main problems in order to accomplish it:
the workload is split into different jobs
the workload is created in two phases (first web-burner-init, then node or cluster density)
A major refactoring is needed to be able to implement the functionality.
Describe alternatives you've consideredhttps://github.com/kube-burner/kube-burner-ocp/pull/77 was a first attempt to implement churn in the web-burner-cluster-density workload. The served namespace(s) gets deleted but when recreated the corresponding served pods are not there as they were created as part of a different job, and the resource validation fails:
time="2024-06-04 08:42:42" level=info msg="Deleting 1 namespaces with label: churndelete=delete" file="namespaces.go:67"
time="2024-06-04 08:43:21" level=info msg="Re-creating deleted objects" file="create.go:374"
time="2024-06-04 08:45:48" level=info msg="Churn job complete" file="create.go:333"
time="2024-06-04 08:45:51" level=info msg="👋 Exiting kube-burner 1de61c31-abe0-4c95-9177-fc7d8a29dfae" file="helpers.go:111"
Running pods in cluster labeled with kube-burner-job=init-served-job different from expected: Expected=1, observed=0
Describe the solution you'd like Add churn to web-burner workload. There are two main problems in order to accomplish it:
A major refactoring is needed to be able to implement the functionality.
Describe alternatives you've considered https://github.com/kube-burner/kube-burner-ocp/pull/77 was a first attempt to implement churn in the web-burner-cluster-density workload. The served namespace(s) gets deleted but when recreated the corresponding served pods are not there as they were created as part of a different job, and the resource validation fails: