website: remove unmaintained distributions

[juliusvonkohout]

I have removed distributions with no git activity for over 1 year and which are at least 5 releases behind.

@kubeflow/kubeflow-steering-committee @thesuperzapper @kimwnasptd

• We still get confused users on the mailing list or slack with a very bad experience https://groups.google.com/g/kubeflow-discuss/c/hI2wH2kGEt0/m/-nWSFAQaAwAJ?utm_medium=email&utm_source=footer
• related to Update of the support page #4021
• I still saw some activity in the last year for the distribution from Microsoft so I left it in, but after the 1.10 release we should remove it as well if they do not update the version
• Also IBM is the next candidate with no commits for a year https://github.com/IBM/manifests.
• Google is similar https://github.com/googlecloudplatform/kubeflow-distribution.
• I could also remove the unmaintained ones from Microsoft, Google and IBM right now and improve the user experience. Outdated distributions really harm our brand and the user experience. They mean that all our efforts in the open source project do not reach the end user.

We had

1.6.0 - > 1.6.1 -> 1.7.0 -> 1.8.0 -> 1.8.1 -> 1.9.0 -> 1.9.1 -> 1.10.0

For example 1.6.0 is from 2022, we now have 2025.

@kubeflow/kubeflow-steering-committee @thesuperzapper @kimwnasptd

[andreyvelich]

Generally, I agree with this change, but let's officially announce the removal using our communication channels and give 2-3 weeks distributions to response.

/hold
/cc @akgraner @StefanoFioravanzo @chasecadet

[akgraner]

I can make an announcement about this on our socials. Sent from Gmail Mobile

…

On Thu, Feb 27, 2025 at 11:11 AM google-oss-prow[bot] < ***@***.***> wrote: @google-oss-prow[bot] requested your review on: #4024 <#4024> Remove unmaintained distributions. — Reply to this email directly, view it on GitHub <#4024 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABPJ3ZJVRKDSWGHUEGVP7TD2R42LFAVCNFSM6AAAAABYAGIRA2VHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJWGQ4TSNJUGU4TMNA> . You are receiving this because your review was requested.Message ID: ***@***.***>

[juliusvonkohout]

I have updated the text a bit.

[StefanoFioravanzo]

I see that the page still says 1.8 for Canonical's Charmed Kubeflow, although we support 1.9 from day one. Since we are about to release 1.10 as well I'l wait to update that one in a few weeks

[juliusvonkohout]

I see that the page still says 1.8 for Canonical's Charmed Kubeflow, although we support 1.9 from day one. Since we are about to release 1.10 as well I'l wait to update that one in a few weeks

@thesuperzapper where do the release version variables for the distributions come from ?

[franciscojavierarceo]

@juliusvonkohout take a look here: https://github.com/kubeflow/website/blob/master/layouts/shortcodes/redhat/latest-version.html

[juliusvonkohout]

I see that the page still says 1.8 for Canonical's Charmed Kubeflow, although we support 1.9 from day one. Since we are about to release 1.10 as well I'l wait to update that one in a few weeks

I just updated it to 1.9.1 since i know you are on 1.9 and you use components as in 1.9.1 e.g. https://discourse.charmhub.io/t/charmed-kubeflow-1-9-updated-to-use-kfp-2-3/16073

[StefanoFioravanzo]

Thank you @juliusvonkohout ! We'll make sure to always keep this page up to date from now on. Thanks again :)

[juliusvonkohout]

I just checked all distributions for the right version again (not just git activity) and found that https://github.com/Azure/kubeflow-aks/releases is 1.8

[juliusvonkohout]

@andreyvelich Cisco just reached out here and the also almost ran into the unmaintained distribution trap https://cloud-native.slack.com/archives/C073N7BMLB1/p1744652589025569?thread_ts=1744627887.610509&cid=C073N7BMLB1

[juliusvonkohout]

See also how we updated charmed Kubeflow #4077 and we could update Nutanix as well @johnugeorge

[juliusvonkohout]

@kubeflow/kubeflow-steering-committee can we approve this PR as a small step to less user confusion https://groups.google.com/g/kubeflow-discuss/c/hI2wH2kGEt0/m/-nWSFAQaAwAJ?utm_medium=email&utm_source=footer Cisco just reached out here and the also almost ran into the unmaintained distribution trap https://cloud-native.slack.com/archives/C073N7BMLB1/p1744652589025569?thread_ts=1744627887.610509&cid=C073N7BMLB1

[andreyvelich]

I think, we should move forward with this PR after we merge this one: #4065
That will allow users to see that Kubeflow Ecosystem is mature and many companies use it in Production.

WDYT @kubeflow/kubeflow-steering-committee ?

[franciscojavierarceo]

i'm good with that

[johnugeorge]

+1

[terrytangyuan]

/lgtm

[juliusvonkohout]

/approve
Then given 80% in favour and 100 % long-term in favour.

[google-oss-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: juliusvonkohout

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:

• OWNERS [juliusvonkohout]

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

[juliusvonkohout]

/unhold