make health options configurable

[nwsparks]

Is this a bug fix or adding new feature?

#1411

#336

What is this PR about? / Why do we need it?

makes health checks configurable for troubleshooting purposes/slow nodes

named the values this way to keep them consistent with the health port definition

What testing is done?

lint/template/kuebconform

[k8s-ci-robot]

Hi @nwsparks. Thanks for your PR.

I'm waiting for a kubernetes-sigs 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-sigs/prow repository.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: nwsparks, seanzatzdev-amazon

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 [seanzatzdev-amazon]

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

[seanzatzdev-amazon]

/lgtm

[k8s-ci-robot]

@nwsparks: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-aws-efs-csi-driver-external-test-eks	b8afd2a	link	true	/test pull-aws-efs-csi-driver-external-test-eks
pull-aws-efs-csi-driver-e2e	b8afd2a	link	true	/test pull-aws-efs-csi-driver-e2e

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

[nwsparks]

/retest

[k8s-ci-robot]

@nwsparks: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

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-sigs/prow repository.

[nwsparks]

the test failures seem unrelated to my changes, appears to have failed during test setup. can someone rerun this?