Change min K8s version to reflect reality

[dprotaso]

• 0.14 min K8s is 1.15
• 0.15 min K8s is 1.16
• 0.16 min K8s will remain 1.16
• 0.17 min K8s will hopefully be 1.17

Delay is due to availability of stable newer version from providers

I didn't bother predicting 0.18 and beyond

[dprotaso]

/assign technical-oversight-committee

[knative-prow-robot]

@dprotaso: GitHub didn't allow me to assign the following users: technical-oversight-committee.

Note that only knative members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign technical-oversight-committee

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.

[dprotaso]

summoning TOC
/assign evankanderson grantr markusthoemmes mattmoor tcnghia

[evankanderson]

Is this just pessimism, or based on actual product announcements?

If we're diverging from the kubernetes upstream release min version, we might also want to update the principles mentioned earlier to call out that we are blocking on one or more of AKS, EKS and GKE.

/lgtm
/approve
/hold

[knative-prow-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dprotaso, evankanderson

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• mechanics/OWNERS [evankanderson]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[dprotaso]

Is this just pessimism, or based on actual product announcements?

0.14 min K8s is 1.15
0.15 min K8s is 1.16

These are amendments to reflect what we supported when we released.

0.16 min K8s will remain 1.16

AKS - Kubernetes version 1.17 will GA on the week of July 1st
GKE - 1.17 is still in the rapid channel
EKS - 1.17 has no release date

Given the lack of availability of 1.17 for the upcoming release I revised it to 1.16.

0.17 min K8s will hopefully be 1.17

The original release is had K8s min version 1.18 - I'm being pessimistic that version will be available

If we're diverging from the kubernetes upstream release min version, we might also want to update the principles mentioned earlier to call out that we are blocking on one or more of AKS, EKS and GKE.

I can bring this up in the ToC meeting to get input but I agree that we need some revisions

[evankanderson]

From Tim Pepper on slack:

k8s community patch backport support is going to be “one year” (for 1.19 and newer) instead of the previous fuzzy “until the 3rd newer release comes out” which tended to give an strange 9 months (or more? or less?) of patch support depending confusingly on the future project’s release dates

I'm willing to approve this for now with an item to come back and update the principles as the K8s community evolves their rules.

[evankanderson]

/hold cancel