Skip to content

Distributions and Kubeflow 1.6 release #2221

@annajung

Description

@annajung

The goal of this issue is to track the progress of distributions alongside the 1.6 release

While we hope all distros will manage to be ready when the KF 1.6 release is out, this is sometimes impossible to achieve. In this issue, we want to both keep track of the progress of distributions toward the KF 1.6 release and also which of the distros will be working on KF 1.6 (testing during the distribution testing cycle) even if they can't meet the KF 1.6 deadline.

Tagging distribution owners identified in the kubeflow/community#560 (Any new or missed distro owners, please comment on the issue to be tracked with the 1.6 release)

Distribution Representatives State
Arrikto EKF @kimwnasptd (stretch goal) participating in 1.6
Arrikto MiniKF @kimwnasptd (stretch goal) participating in 1.6
AWS @surajkota helping with testing in 1.6
Charmed Kubeflow @DomFleischmann participating in 1.6
Google Cloud @zijianjoy @gkcalat participating in 1.6
IBM @yhwang participating in 1.6
Nutanix @johnugeorge participating in 1.6
Kubeflow with Argo CD @davidspek
Openshift @VaishnaviHire @LaVLaS participating in 1.6
Oracle Cloud Infrastructure @julioo participating in 1.6

Please let us know if you'll be participating in the 1.6 release by answering the following questions:

  • Are you planning on having your distro ready in sync with the KF 1.6 release?
  • Will you participate by testing your distro during the distribution testing phase and providing feedback (reporting any issues to the release team)?
  • If you cannot participate, when can the community expect your distro to be ready for release 1.6?

[Update on June 14th] Distribution testing is scheduled to take place from July 20th to August 10th
Note: After the 2 weeks delay, distribution testing is now scheduled to take place from July 6th to July 27th (ref kubeflow/community#561)

cc @kubeflow/release-team @jbottum

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions