Add resource limits to Ansible operator scaffolding

[asmacdo]

The Helm operator scaffolds resource limits in the manager manifest:

operator-sdk/internal/plugins/helm/v1/scaffolds/internal/templates/config/manager/manager.go

Lines 78 to 84 in 24d73f7

	resources:
	limits:
	cpu: 100m
	memory: 90Mi
	requests:
	cpu: 100m
	memory: 60Mi

However these resource limits were too restrictive for ansible operators. Since v0.19 scaffolded Ansible operators do not have resource limits, I am considering this a new feature that can be added post 1.0 release.

[camilamacedo86]

It is important because common attacks take advantage of it. See; https://cheatsheetseries.owasp.org/cheatsheets/Docker_Security_Cheat_Sheet.html#rule-7-limit-resources-memory-cpu-file-descriptors-processes-restarts

PS. The default values are not enough for Ansible. So, the complexity here is to find what values should be appropriated.

[asmacdo]

Some research is needed to determine what these default values should be. We have deprioritized for now-- please feel free to chime in or open a PR with suggested defaults.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[camilamacedo86]

/lifecycle frozen

[camilamacedo86]

@asmacdo, @fabianvf, @jmrodri shows like we need to be priorized this one.
I started to work on some POC tests to address this need.

We need to have default values that work for our samples, note that users will be notified that they ought to optimize the values based on their projects. See: https://github.com/operator-framework/operator-sdk/pull/5330/files#diff-063b9bbaede872aca0d6afe93d010d359c86cbc7ad4c1eab8652d8a5a46f6158R50-R51

It was also added in the docs:

Optimize manager resource values in config/manager/manager.yaml according to project requirements. It is recommended to define resources limits in order to follow good practices and for security reasons. More info: Managing Resources for Containers and Docker Security Cheat Sheet

https://sdk.operatorframework.io/docs/best-practices/common-recommendation/

And then, see: operator-framework/api#172