Skip to content

website: Remove outdated distributions#4429

Open
juliusvonkohout wants to merge 1 commit into
masterfrom
remove-outdated-distributions
Open

website: Remove outdated distributions#4429
juliusvonkohout wants to merge 1 commit into
masterfrom
remove-outdated-distributions

Conversation

@juliusvonkohout

@juliusvonkohout juliusvonkohout commented Jul 10, 2026

Copy link
Copy Markdown
Member

Description of Changes

The KSC has voted and approved kubeflow/community#1002

so

For AKS @ritazh @mosabami @asw101 as in #4153
For Nutanix @johnugeorge #4122
For QBO @alexeadem #4111

please update your distributions.

We had 1.10.0 -> 1.10.1 -> 1.10.2 -> 1.11.0 -> 26.03.0 -> 26.03.1 https://github.com/kubeflow/community-distribution/releases, so some of your distribution are missing out for 5 releases.

"If a distribution no longer qualifies to be listed as a Kubeflow Distribution, its owners will
be notified of the reasons why via their contact details and will have 90 days to implement the
necessary changes.

If the distribution owners do not implement the changes or do not respond to requests, then the
distribution will be removed and will no longer be listed in the Kubeflow website."

You qualify hereby as notified.
cc @kubeflow/kubeflow-distribution-committee and @kubeflow/kubeflow-steering-committee

Related Issues

#4406

Signed-off-by: Julius von Kohout <[email protected]>
@google-oss-prow google-oss-prow Bot added the area/community AREA: Community Docs label Jul 10, 2026
@google-oss-prow
google-oss-prow Bot requested review from alfsuse and knkski July 10, 2026 15:36
@google-oss-prow

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from juliusvonkohout. For more information see the Kubernetes Code Review Process.

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

Details Needs approval from an approver in each of these files:

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

@juliusvonkohout

Copy link
Copy Markdown
Member Author

For ProKube @geier in autumn with the next release Prokube is also too far behind.

@juliusvonkohout

Copy link
Copy Markdown
Member Author

For canonical @deusebio #4366 in autumn with the next release charmed Kubeflow is also too far behind.

@christian-heusel

christian-heusel commented Jul 10, 2026

Copy link
Copy Markdown
Member

@juliusvonkohout as far as I understood the full range of 26.03 (n) - 1.11(n-1) - 1.10 (n-2) is still fine to be listed on the website since it's about two major versions (patch releases are not listed on https://www.kubeflow.org/docs/kubeflow-distribution/releases/) as defined by the linked policy.

(I don't have any involvement in the distributions listed there; just for transparency)

cc @andreyvelich @chasecadet @thesuperzapper @franciscojavierarceo who know more around the intent of the new policy: I added kubeflow/community#1015 to clarify the wording

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/community AREA: Community Docs size/M

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants