[ACTION] Modify flux resources for Falco to support pipeline

[rossf7]

Task Description

To support the deploy step changes in https://github.com/cncf-tags/green-reviews-tooling/issues/99 we need to modify the flux resources we use to deploy Falco.

We need to sync with the Falco team on the changes.

Current State

• Falco is deployed 24/7 using flux with the resources in clusters/projects/falco
• This references the https://github.com/falcosecurity/cncf-green-review-testing repo maintained by the Falco team
• Resources for all 3 falco drivers are created but only modern-ebpf pods are scheduled due to node labels

Desired State

• Falco is only deployed during a run of the green review pipeline
• config input is used so only resources for a single Falco driver are created
• version input is used to template the container image that is deployed
• New node selector used for all drivers node-role.kubernetes.io/benchmark: "true"

Tasks

• [ ] Delete flux resources from green-reviews-tooling so falco is not deployed 24/7 - code
• [ ] Refactor flux resources in falcosecurity/cncf-green-review-testing to support new inputs - spec

[rossf7]

Status

@nikimanoledaki @AntonioDiTuri Posting an update here as part of my handover since I'll be off till 15th July. Lets discuss in our sync.

Changes to the Falco manifests are proposed in this discussion.

If Falco team are happy with the changes then once merged we need to update each kustomization resource to use the new paths.

e.g. https://github.com/cncf-tags/green-reviews-tooling/blob/main/projects/falco/ebpf.yaml#L19

path: ./kustomize/falco-driver/ebpf

This PR has cluster changes to support the deploy step https://github.com/cncf-tags/green-reviews-tooling/pull/111