fix(KubeArmor helm): added resources property in values.yaml file

[FernandoPazCavalcante]

Purpose of PR?: Parameterize deployments resources configuration for KubeArmor HelmChart

Fixes #

Does this PR introduce a breaking change?
no

If the changes in this PR are manually verified, list down the scenarios covered::
I've been using this helm chart for some months and then it suddenly crashed my AWS EC2 instance due to exceed memory usage. There were a lack of setup at my side, but some kind of memory limit should be available to be set up in this helm chart.

Additional information for reviewer? :
Added resources parameterization in values.yaml with default request value
edit: added resources property in kubearmorController and kubearmorRelay deployments.

Checklist:

• Bug fix. Fixes #
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update
• PR Title follows the convention of <type>(<scope>): <subject>
• Commit has unit tests
• Commit has integration tests

[rksharma95]

@FernandoPazCavalcante thanks for the PR, default deployment method is kubearmor-operator can we handle it there as well?

[AlissonRS]

@FernandoPazCavalcante I'd also recommend adding resources to the daemonset.

[FernandoPazCavalcante]

@FernandoPazCavalcante thanks for the PR, default deployment method is kubearmor-operator can we handle it there as well?

The kubearmor-operator already has this resource management property but it was missing in kubearmor helm chart. I also added it to the DaemonSet as requested by @AlissonRS

[AlissonRS]

@rksharma95 do you think this PR is good enough for merging, based on @FernandoPazCavalcante's comment above?

[rksharma95]

@AlissonRS @FernandoPazCavalcante it's fine If kubearmor helm chart being used for deployment.
when kubearmor-operator being used for deployment, the resource configuration present with operator helm chart will deploy kubearmor-operator with this resource limits, but it will not be passed to other deployments, daemonset. as operator generates and deploy k8s resource i.e. deployment, daemonset, etc as part of it.

let me know if this meets your requirements in that case we can definitely merge this PR. thanks again for the PR @FernandoPazCavalcante 🙌

[FernandoPazCavalcante]

@AlissonRS @FernandoPazCavalcante it's fine If kubearmor helm chart being used for deployment. when kubearmor-operator being used for deployment, the resource configuration present with operator helm chart will deploy kubearmor-operator with this resource limits, but it will not be passed to other deployments, daemonset. as operator generates and deploy k8s resource i.e. deployment, daemonset, etc as part of it.

let me know if this meets your requirements in that case we can definitely merge this PR. thanks again for the PR @FernandoPazCavalcante 🙌

Yes, these changes definitely meet our needs since I need to define resource requests and limits, and this is the chart we use in my team. Thank you very much. 🙏

[rksharma95]

Yes, these changes definitely meet our needs since I need to define resource requests and limits, and this is the chart we use in my team. Thank you very much. 🙏

Thanks for update, We can start review, will merge after then. thanks again for the PR

[rksharma95]

LGTM 👍