Add quoting to sysctls because numeric values need to be strings

[towolf]

What this PR does / why we need it:

Sorry, I missed this problem with my previous PR #5752:

Error: DaemonSet in version "v1" cannot be handled as a DaemonSet: v1.DaemonSet.Spec: v1.DaemonSetSpec.Template: v1.PodTemplateSpec.Spec: v1.PodSpec.SecurityContext: v1.PodSecurityContext.Sysctls: []v1.Sysctl: v1. Sysctl.Value: ReadString: expects " or n, but found 8, error found in #10 byte of ...|,"value":8192}]},"se|..., bigger context ...|{"sysctls":[{"name":"net.core.somaxconn","value":8192}]},"serviceAccountName":"...

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)

How Has This Been Tested?

Tested with numeric values for sysctls:

        sysctls:
        - name: "net.core.somaxconn"
          value: "8192"

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]

Hi @towolf. 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.

[aledbf]

/ok-to-test

[aledbf]

/lgtm
/approve

[aledbf]

@towolf thanks!

[aledbf]

/retest

[aledbf]

/retest

[aledbf]

/retest

[aledbf]

@towolf just in case, the errors are not related to the PR itself but slow prow jobs

[towolf]

Yeah, keep 'em coming!

[aledbf]

/retest

[aledbf]

/retest

[aledbf]

/retest

[cmluciano]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aledbf, cmluciano, towolf

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 [aledbf]

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

[aledbf]

/retest

[aledbf]

/retest

[aledbf]

/retest

[aledbf]

/retest

[aledbf]

/retest

[aledbf]

/retest

[aledbf]

/retest

[aledbf]

/retest

[aledbf]

/retest

[aledbf]

/retest

[aledbf]

/retest

[k8s-ci-robot]

@towolf: The following test failed, say /retest to rerun all failed tests:

Test name	Commit	Details	Rerun command
pull-ingress-nginx-e2e-helm-chart	f7a24e9	link	/test pull-ingress-nginx-e2e-helm-chart

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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. I understand the commands that are listed here.