New Linter: nodurations

[JoelSpeed]

• Durations should be avoided and should instead use fooSeconds, avoids having to implement go duration parsing

[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

[JoelSpeed]

/remove-lifecycle stale
/lifecycle frozen

[Karthik-K-N]

/assign

[Karthik-K-N]

I have done basic analysis for the linter.

1. I think we need to check the type fields to make sure its not of Duration type"
2. Duration can be of tiime.Duration or metav1.Duration (are there any other?)
3. I think I can't use the existing type checker as it looks for built in type and Duration is not.

@JoelSpeed any inputs here. Thanks.

[JoelSpeed]

I think your analysis sounds correct to me, will hopefully be similar to others!