Fix TerminationGracePeriodSeconds is negative

[wzshiming]

• Firstly release 1.22 Fix TerminationGracePeriodSeconds is negative (part 1) #98866:
  • Treat negative as 1 in delete path (pod/strategy.go, apiserver delete.go)
  • Allow delete with grace period 0 even if metadata period is negative (apiserver delete.go). This allows kubelet to delete pods.
  • Relax validation of immutable fields to allow it to be set to 1 if it was previously negative. This allows us to update read path in the next release. All consumers would also need to be able to handle this change in a sane manner.
• Secondly release 1.27 pod.spec.terminationGracePeriodSeconds is a negative then convert to 1 #115606:
  • Treat negative as 1 (defaulting or conversion)
• Thirdly:
  • Returning an error on Pod create could break things like Deployment updates. But if we update defaulting, then I think we won't hit this issue.

What would you like to be added:

#98866 (comment)

Why is this needed:

[wzshiming]

/assign

[wzshiming]

/sig node
/triage accepted
/lifecycle frozen

[k8s-triage-robot]

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

[k8s-ci-robot]

This issue is currently awaiting triage.

If a SIG or subproject 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.