Conformance profiles

[johnbelamaric]

Enhancement Description

• One-line enhancement description (can be used as a release note): Define and implement tooling to support conformance profiles
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-architecture/1618-conformance-profiles
• Primary contact (assignee): @johnbelamaric
• Responsible SIGs: SIG Architecture
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y)
  • Beta release target (x.y)
  • Stable release target (1.19) (this is a tooling change)

[johnbelamaric]

/sig architecture
/priority important-soon
/assign

[spiffxp]

summary and motivation: #1619

[kikisdeliveryservice]

Hi @johnbelamaric 😄

1.19 Enhancements shadow here. I wanted to confirm that 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]

Hi John,

I see that the underlying KEP as merged but is marked as provisional, will this be moved to implementable along with test plans by next Tuesday for inclusion in 1.19?

Thanks!

[palnabarun]

According to conversation with @johnbelamaric on Slack, this won't graduate it 1.19 and instead should be pushed to 1.20.

/milestone v1.20

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[spiffxp]

/remove-lifecycle stale

[kikisdeliveryservice]

Hi @johnbelamaric 😄

Enhancements Lead here. Is this still going for GA in 1.20?

Thanks!
Kirsten

[kikisdeliveryservice]

Hey @johnbelamaric

Just wanted to double check on this for 1.20? Any plans?

[kikisdeliveryservice]

As a reminder Enhancements Freeze is October 6th. This KEP is still provisional and lacks graduation criteria. If you would like to be tracked please let me know.

[kikisdeliveryservice]

Enhancements Freeze is now in effect. If you wish to be included in the 1.20 Release, please submit an Exception Request as soon as possible.

Best,
Kirsten
1.20 Enhancements Lead

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

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.