Allow running berserker on k8s with configuration

[Molter73]

This PR adds a basic yaml file that allows running berserker as a daemon set and use configmaps to control its behavior.

For now the image being configured is one on quay.io/rhacs-eng/qa, but it'd be great to update it to a tagged version if we ever do one of those.

[JoukoVirtanen]

Update to the latest tag 1.0-40-ge3bd96aa5a

[JoukoVirtanen]

You may want to add an imagePullSecret. Currently this doesn't work on infra, because it cannot pull the image.

I don't know if I did this the best way, but you can look at how I did this for the long running cluster. Also you will need to make some changes as this is for kube-burner. ACS itself has some other method for setting imagePullSecrets.

Secret template
https://github.com/stackrox/stackrox/blob/master/scripts/release-tools/kube-burner-configs/secret_template.yml

Berserker deployment that uses the secret
https://github.com/stackrox/stackrox/blob/master/scripts/release-tools/kube-burner-configs/cluster-density/deployment.yml

Script that creates the secret from the secret template
https://github.com/stackrox/actions/blob/main/release/start-kube-burner/start-kube-burner.sh

[JoukoVirtanen]

I did the following test

minikube start --driver=docker --cpus=10 --memory=29000 

minikube ssh

docker login quay.io

docker pull quay.io/rhacs-eng/qa:berserker-1.0-35-g3d1715a7f3
docker pull quay.io/rhacs-eng/qa:berserker-1.0-40-ge3bd96aa5a

exit

kubectl create -f endpoints-uniform.yml
kubectl create -f berserker.yml

In a separate terminal run any of the collector integration tests

make -C integration-tests TestChangeProcessNameChildProcessNoFork COLLECTOR_TAG=3.16.x-82-gf1e4d3ca19

This integration test doesn't exist in the master branch but any of them will do

grep berserker TestChangeProcessNameChildProcessNoFork-events.log

When using the berserker-1.0-35-g3d1715a7f3 no endpoints are observed

kubectl edit ds/berserker

Change the image tag to berserker-1.0-40-ge3bd96aa5a

Run the collector integration test again

grep berserker TestChangeProcessNameChildProcessNoFork-events.log

2023/10/08 12:16:27 EndpointInfo: SOCKET_FAMILY_IPV4|L4_PROTOCOL_TCP|address_data:"\000\000\000\000" port:3624 ip_network:"\000\000\000\000 " |(timestamp: nil Timestamp)|process_name:"berserker" process_exec_file_path:"/usr/local/bin/berserker" 
2023/10/08 12:16:27 EndpointInfo: SOCKET_FAMILY_IPV4|L4_PROTOCOL_TCP|address_data:"\000\000\000\000" port:1480 ip_network:"\000\000\000\000 " |(timestamp: nil Timestamp)|process_name:"berserker" process_exec_file_path:"/usr/local/bin/berserker" 
2023/10/08 12:16:27 EndpointInfo: SOCKET_FAMILY_IPV4|L4_PROTOCOL_TCP|address_data:"\000\000\000\000" port:3625 ip_network:"\000\000\000\000 " |(timestamp: nil Timestamp)|process_name:"berserker" process_exec_file_path:"/usr/local/bin/berserker" 
2023/10/08 12:16:27 EndpointInfo: SOCKET_FAMILY_IPV4|L4_PROTOCOL_TCP|address_data:"\000\000\000\000" port:3626 ip_network:"\000\000\000\000 " |(timestamp: nil Timestamp)|process_name:"berserker" process_exec_file_path:"/usr/local/bin/berserker"

Many other endpoints are observed.

Repeat the test for the other config files.

[JoukoVirtanen]

Perhaps in the future we could have some integration tests to make sure that we are getting the desired load from berserker.

[JoukoVirtanen]

[ultra nit] The other files don't start with a blank space.

[JoukoVirtanen]

The file names could be improved. They could be either prefixed or suffixed with the kind. E.g berserker-daemonset.yml.