Add default limits to CR

[jotak]

(it makes it easier to tune these limits by modifying the CR)

side question: should we change these limit? E.g. raise to, maybe, 800 Mi ?

[jpinsonneau]

If we do that for FLP, should we do it for all components ?

We also need to keep synced this with defaults values from api/v1alpha1/flowcollector_types.go
FYI there is also a PR pending for missing config of eBPF agent: #155

[jotak]

If we do that for FLP, should we do it for all components ?

Yes and it's not just for req/limits, pretty much all options could be defaulted in the sample CR, it helps to have a CR that we can tune without having to refer to any documentation. (I thought we were already doing that, but maybe I was the only one lol)

[jotak]

@jpinsonneau I added the ebpf limits following what you did in your PR. We should merge them +/- together for consistency.
(I haven't tested mine yet, fussy cluster this morning :/ )

[jotak]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jotak

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [jotak]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment