Enhancements: Enable running conformance tests without beta REST APIs or features

[liggitt]

Enable running conformance tests without beta REST APIs or features

• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/blob/master/keps/sig-architecture/20191023-conformance-without-beta.md
• Primary contact (assignee): @liggitt
• Responsible SIGs: sig-architecture
• Enhancement target:
  
  
  
  • Phase 1: v1.18
  
  
  • Phase 2: v1.19
  
  
  • Phase 3: intersects with conformance profiles (https://github.com/kubernetes/enhancements/issues/1618)
  
  

[palnabarun]

Hey there @liggitt -- 1.18 Enhancements shadow here. I wanted to check in and see if you think this Enhancement will be graduating to alpha in 1.18 or having a major change in its current level?

The current release schedule is:

• Monday, January 6th - Release Cycle Begins
• Tuesday, January 28th EOD PST - Enhancements Freeze
• Thursday, March 5th, EOD PST - Code Freeze
• Monday, March 16th - Docs must be completed and reviewed
• Tuesday, March 24th - Kubernetes 1.18.0 Released

To be included in the release,

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

If you would like to include this enhancement, once coding begins please list all relevant k/k PRs in this issue so they can be tracked properly. 👍

We'll be tracking enhancements here: http://bit.ly/k8s-1-18-enhancements

Thanks! :)

[liggitt]

This is targeting phase 1 (defined in the KEP) in v1.18

[palnabarun]

Thank you @liggitt for the updates. :)

[jeremyrickard]

/milestone v1.18

[palnabarun]

Hi @liggitt, just a friendly reminder that the Code Freeze will go into effect on Thursday 5th March.

Can you please link all the k/k PRs or any other PRs which should be tracked for this enhancement?

Thank You :)

[VineethReddy02]

Hello, @liggitt I'm 1.18 docs lead.
Does this enhancement work planned for 1.18 require any new docs (or modifications to existing docs)? If not, can you please update the 1.18 Enhancement Tracker Sheet (or let me know and I'll do so)
If so, just a friendly reminder we're looking for a PR against k/website (branch dev-1.18) due by Friday, Feb 28th, it can just be a placeholder PR at this time. Let me know if you have any questions!

[liggitt]

probably no docs for the work done on this in 1.18 (this is focused on a CI/test aspect of our dev process)

[jeremyrickard]

Hi @liggitt, just a friendly reminder that the Code Freeze will go into effect on Thursday 5th March.

Can you please link all the k/k PRs or any other PRs which should be tracked for this enhancement?

Thank You :)

[liggitt]

This is not delivering code in k/k this release, this "enhancement" consists of additional test jobs/configurations that are not release-blocking

[liggitt]

Relevant PRs are open at:

• https://github.com/kubernetes-sigs/kind/pull/1378
• https://github.com/kubernetes/test-infra/pull/16560

[liggitt]

/milestone v1.19

Once CSR graduates to v1, this will update to complete phase 2

[harshanarayana]

Hey there @liggitt, 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:

1. The KEP PR must be merged in an implementable state
2. The KEP must have test plans
3. 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

If you do, 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!

[liggitt]

Once CSR graduates to v1, this will update to complete phase 2 (planned for 1.19)

[harshanarayana]

Hi @liggitt thanks for following up with an update on the status. I will update the tracking sheets accordingly.

[palnabarun]

/stage beta

[mikejoh]

Hello, @liggitt ! :wave: I'm one of the v1.19 Docs shadows. Does this enhancement work planned for v1.19 require any new docs (or modifications to existing docs)?

This is a friendly reminder that we're looking for a PR against kubernetes/website (branch dev-1.19) due by Friday, June 12, it can just be a placeholder PR at this time. Let me know if you have any questions!

I saw that you've commented the following on this issue:

probably no docs for the work done on this in 1.18 (this is focused on a CI/test aspect of our dev process)

Reading up a bit on this enhancement and the fact that the checklist in the KEP document have docs crossed over there may not be a need for docs?

Regards,
Mikael.

[liggitt]

No docs changes required

[harshanarayana]

Hey @liggitt, I am with the enhancements team for the v1.19 release cycle as a shadow.

The code freeze deadline for the Enhancement is Thursday, June 25. I am checking in to see if there is any k/k PR that you have already opened for this enhancement and if so, would you be able to point me in the direction of the PR so that the same can be updated in the tracking sheet

Have a wonderful day. 🖖

[liggitt]

The only PR for this will be against https://github.com/kubernetes-sigs/kind/ to adjust the configuration of the conformance-only CI job

[harshanarayana]

Thanks @liggitt for the clarification. 🖖

[harshanarayana]

Hi, @liggitt,

This is a follow-up to the communication that went out to k-dev today. There has been a revision to the release schedule of v1.19 as follows.

Thursday, July 9th: Week 13 - Code Freeze
Thursday, July 16th: Week 14 - Docs must be completed and reviewed
Tuesday, August 25th: Week 20 - Kubernetes v1.19.0 released
Thursday, August 27th: Week 20 - Release Retrospective

You can find the revised Schedule in the sig-release Repo

Please let me know if you have any questions. 🖖

[liggitt]

Running conformance tests without beta APIs for features is now complete for 1.19.

The final phase of the KEP is still pending - identifying which GA APIs are required for conformance and running conformance tests without optional GA APIs enabled.

[palnabarun]

This is now complete.

@liggitt -- Can you please mark the KEP as implemented so that we can close this issue? :slightly_smiling_face:

[liggitt]

The KEP had additional phases added to it related to identifying optional GA APIs. That phase has not been implemented.

[kikisdeliveryservice]

/milestone clear

(removing this enhancement issue from the v1.19 milestone as the milestone is complete)

[kikisdeliveryservice]

Hi @liggitt

Enhancements Lead here. Any plans for this in 1.20?

Thanks!
Kirsten

[liggitt]

Not for 1.20... linked to the conformance profiles issue the third phase intersects with