provide recommended .status.conditions schema

[deads2k]

provide recommended .status.conditions schema

• Provide a standard .status.conditions schema and golang type:
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/1623-standardize-conditions
• Primary contact (assignee): @deads2k
• Responsible SIGs: @kubernetes/sig-api-machinery-api-reviews @kubernetes/sig-architecture-api-reviews
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y)
  • Beta release target (x.y)
  • Stable release target (x.y) 1.19

[lavalamp]

+1

@etune @liggitt fyi

I'd like to suggest the current pattern should add:

• Observed generation field (what version of the spec is this condition about, if applicable?
• Identity field (what controller / actor observed this condition)? (possibly, we could use the fieldManager instead of adding a field.)

Both would make multiple controller interactions simpler / more transparent. (Think: kubelet / NPD / node controller)

[kikisdeliveryservice]

Hi @deads2k !

1.19 Enhancements shadow here. I wanted to check in and see if you think this Enhancement will be graduating in 1.19?

In order to have this part of the release:

The KEP PR must be merged in an implementable state
The KEP must have test plans
The KEP must have graduation criteria.

The current release schedule is:

Monday, April 13: Week 1 - Release cycle begins
Tuesday, May 19: Week 6 - Enhancements Freeze
Thursday, June 25: Week 11 - Code Freeze
Thursday, July 9: Week 14 - Docs must be completed and reviewed
Tuesday, August 4: Week 17 - Kubernetes v1.19.0 released

Please let me know and I'll add it to the 1.19 tracking sheet (http://bit.ly/k8s-1-19-enhancements). Once coding begins please list all relevant k/k PRs in this issue so they can be tracked properly. 👍

Thanks!

[kikisdeliveryservice]

/tracked yes

[kikisdeliveryservice]

/milestone 1.19

[k8s-ci-robot]

@kikisdeliveryservice: The provided milestone is not valid for this repository. Milestones in this repository: [keps-beta, keps-ga, v1.17, v1.18, v1.19, v1.20, v1.21]

Use /milestone clear to clear the milestone.

In response to this:

/milestone 1.19

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.

[kikisdeliveryservice]

/milestone v1.19

[kikisdeliveryservice]

Hi @deads2k

As a quick note: #1620 merged recently, adding production readiness review questions to the KEP template. We are not making it mandatory for the 1.19 release cycle, but it would be great if the PRR questionnaire is filled. You can find the template at https://github.com/kubernetes/enhancements/tree/master/keps/NNNN-kep-template

Thanks!