Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Auto generate the version-skew-policy.md file #14307

Closed
Rajakavitha1 opened this issue May 14, 2019 · 9 comments · Fixed by #20369
Closed

Auto generate the version-skew-policy.md file #14307

Rajakavitha1 opened this issue May 14, 2019 · 9 comments · Fixed by #20369
Assignees
@tpepper @zacharysarah @jimangel
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/backlog Higher priority than priority/awaiting-more-evidence.

Comments

@Rajakavitha1
Copy link
Contributor

Rajakavitha1 commented May 14, 2019 •
edited

Auto generate the version-skew-policy.md file (https://kubernetes.io/docs/setup/version-skew-policy/), https://kubernetes.io/docs/setup/independent/create-cluster-kubeadm/#version-skew-policy

What would you like to be added
Auto generate the page based on some basic logic following the skew guidelines and the config.toml located at https://github.com/kubernetes/website/blob/master/config.toml#L80 (for the current release / previous). Include a short description about k/website supporting 5 versions and k/k supporting 3 versions (and calling those out). This page would be generated on build or updated with a hack/script (vs. manual edits)

Why is this needed
There has been requests from vendors to send customers a link that provides details about which releases are currently supported (be that because of an exception or any other reason). This request has be raised in many forums.

Comments
Build logical steps in the k/k release patch process to update our website vars with current minor patch release # in https://github.com/kubernetes/website/blob/master/config.toml#L80
@Rajakavitha1
Copy link
Contributor Author

/assign @jimangel
/assign @zacharysarah
/assign @tpepper

@sftim sftim mentioned this issue Jun 24, 2019
Closed
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 13, 2019
@jimangel
Copy link
Member

jimangel commented Sep 4, 2019

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 4, 2019
@sftim
Copy link
Contributor

sftim commented Sep 10, 2019

/priority backlog
/kind feature

@k8s-ci-robot k8s-ci-robot added priority/backlog Higher priority than priority/awaiting-more-evidence. kind/feature Categorizes issue or PR as related to a new feature. labels Sep 10, 2019
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 9, 2019
@sftim
Copy link
Contributor

sftim commented Dec 10, 2019

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 10, 2019
@jimangel jimangel mentioned this issue Jan 9, 2020
Merged
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 9, 2020
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Apr 8, 2020
@jimangel
Copy link
Member

/remove-lifecycle rotten

@k8s-ci-robot k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Apr 16, 2020
@jimangel jimangel mentioned this issue Apr 16, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tpepper tpepper

@zacharysarah zacharysarah

@jimangel jimangel

Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Automating Version Skew jimangel/website
7 participants
@tpepper @zacharysarah @jimangel @k8s-ci-robot @sftim @fejta-bot @Rajakavitha1