Add kubeflow 1.6 release page

[annajung]

Signed-off-by: Anna Jung (VMware) antheaj@vmware.com

• Add 1.6 release page
• Some links are not available yet
  • 1.6 blog (pr not open yet, should be open before Aug 31st)
  • Updated roadmap (open pr: Update release due date to Aug and link to timeline kubeflow#6508)
  • Final kubeflow 1.6 release tag (available on Sept 7th - release day)
  • Final notebook 1.6 release tag (available before Aug 31st)

cc @kubeflow/release-team

/hold until docs deadline Aug 31st

[annajung]

deploy preview: https://deploy-preview-3332--competent-brattain-de2d6d.netlify.app/docs/releases/kubeflow-1.6/

[zijianjoy]

/lgtm
/approve

Feel free to unhold based on your schedule.

[zijianjoy]

Non-blocking: It will be great to have a list of K8S versions we support in this release.

[annajung]

that's a great idea! I updated the page to include all dependencies that we tracked for the release. PTAL https://deploy-preview-3332--competent-brattain-de2d6d.netlify.app/docs/releases/kubeflow-1.6/

[zijianjoy]

Looks good! Thank you Anna!

[annajung]

@kubeflow/release-team updated to include kustomize into the dependency list - PTAL

[annajung]

Hi everyone, can I get another review (lgtm) for the dependency version table that was added?
aiming to get this merged before the release branch is cut

cc @kubeflow/release-team @zijianjoy

[annajung]

will hold until the 1.6 release day

[zijianjoy]

/lgtm
/approve

Feel free to unhold when the time comes to 1.6 release

[google-oss-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: annajung, zijianjoy

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:

• content/en/docs/releases/OWNERS [zijianjoy]

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

[annajung]

/hold cancel

[thesuperzapper]

@annajung are you sure that we require Kubernetes 1.22 as a minimum (along with the other dependencies listed in the table)? Because right now we are implying that you "must" use the versions of the dependencies listed, which may prevent people from updating to 1.6.0.

I think we can make 3 improvements to that table:

1. Define a "range" of validated/tested versions for each dependency
2. Add a link to a page on kubeflow/manifests that describes how versions are tested/validated
3. Update the language to say "validated/tested dependency versions" rather than "dependency versions"
   • Obviously, we don't yet know if unreleased versions of the dependencies will work fine, so it makes more sense to update that language.

[annajung]

@thesuperzapper the dependency version lists what manifest WG tested with to validate the 1.6 release. It is correct that the Kubeflow release team and manifest cannot recommend any other version to be used other than listed as it was not fully tested with any other version.

My understanding is that manifest group will continue to improve the tests and hope we can define list of range of version, but that was not the case for 1.6