health should be configurable in the helm chart

[nwsparks]

the efs-plugin is frequently failing it's liveness probe on startup. I believe the current configuration in the helm chart is set to check too frequently (period: 2)

it would be simple to change this to allow configuration via helm values. to keep it in line with the existing healthPort I would propose adding the following to the controller and node sections.

  healthInitialDelaySeconds: 10
  healthTimeoutSeconds: 3
  healthPeriodSeconds: 10
  healthFailureThreshold: 5

I can raise a PR.

[seanzatzdev-amazon]

Can you provide logs & raise that PR?

[nwsparks]

sorry for the delay. I can.

logs generally look like this. a bit tough to determine exactly what's happening here, my initial thought was looking at raising the initialdelay which brought me here.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[nwsparks]

pr is open #1428