Helm - Enable configuring request and limit for containers in webhook jobs

[bhumijgupta]

What this PR does / why we need it:

This PR adds two additional fields in helm values namely controller.admissionWebhooks.createSecretJob.resources and controller.admissionWebhooks.patchWebhookJob.resources that can be used to configure the container resources limits and requests for job-createSecret and job-patchWebhook.
By default, the values are empty object, and no explicit resource limits are set by the user.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Which issue/s this PR fixes

Fixes #7105

How Has This Been Tested?

Ran automated tests make kind-e2e-chart-tests and manually deployed the helm chart and checked resources request and limits in the jobs

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I've read the CONTRIBUTION guide
• I have added tests to cover my changes.
• All new and existing tests passed.

[k8s-ci-robot]

@bhumijgupta: This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[k8s-ci-robot]

Hi @bhumijgupta. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[rikatz]

@bhumijgupta thanks for the PR.

Left some minor comment.

Also, would be good to add some e2e test, which would be basically adding a new file in https://github.com/kubernetes/ingress-nginx/tree/main/charts/ingress-nginx/ci with some random values that should work in resources for both files :)

[rikatz]

/ok-to-test

[bhumijgupta]

Added test and addressed the review comments

[bhumijgupta]

/kind feature

[tao12345666333]

LGTM

I need to test locally later

[rikatz]

CI is catching stuff :)
/lgtm
/approve
Thanks!

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bhumijgupta, rikatz

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:

• charts/ingress-nginx/OWNERS [rikatz]

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