Render list of releases using a content adapter
This is a Feature Request
What would you like to be added ~Partially~ Revise https://kubernetes.io/releases/ to have some pages rendered using a content adapter.
For example:
- https://kubernetes.io/releases/v1.30.0/ becomes a new page about the v1.30.0 release
- …with a link to the announcement blog article.
- There are download links (and signatures, etc)
- There's a link to the changelog
- there's a link to the tag at GitHub
- https://kubernetes.io/releases/v1.30.1/ becomes a new page about the v1.30.1 patch release with some details
- and a link to https://kubernetes.io/releases/v1.30.0/
- There are download links etc
- There's a link to the changelog
- There's a link to the tag at GitHub
- https://kubernetes.io/releases/v1.29.0/ becomes a new page about the v1.29.0 release
- …with a link to the announcement blog article
- There are download links (and signatures, etc)
- There's a link to the changelog
- There's a link to the v1.29 documentation
- https://kubernetes.io/releases/v1.19.0/ becomes a new page about the v1.19.0 release
- …with a link to the announcement blog article
- There are download links (and signatures, etc)
- There's a link to the changelog
- https://kubernetes.io/releases/v1.12.3/ becomes a new stub page with details of the v1.12.3 patch release.
- there's a link to the tag at GitHub
- and a link to https://kubernetes.io/releases/v1.12.3/
- but no download links because we don't offer downloads for releases that old
Why is this needed It provides a better place and “one stop shop” for people who want to find out about our releases, new and old.
Comments /area web-development /sig release
We would need to be using Hugo v0.126 or later.
We should only make this change if we think it's a good idea.
+1 from me for this. This looks like a nice feature to incorporate.
This is a great idea. I want to try this for https://github.com/kubernetes/sig-security/issues/1 to auto-generate CVE pages.
Can I request SIG Docs to create a container image that supports this new feature in v0.126.0? Getting this error right now:
personal-macbook:website pushkarj$ make container-serve
"docker" run --rm --interactive --tty --volume "/Users/pushkarj/opensource-ftw/kubernetes/website:/src:ro,Z" --cap-drop=ALL --cap-add=AUDIT_WRITE --read-only --mount type=tmpfs,destination=/tmp,tmpfs-mode=01777 -p 1313:1313 gcr.io/k8s-staging-sig-docs/k8s-website-hugo:v0.126.0-663380dd60a2 hugo server --buildFuture --environment development --bind 0.0.0.0 --destination /tmp/hugo --cleanDestinationDir --noBuildLock
Unable to find image 'gcr.io/k8s-staging-sig-docs/k8s-website-hugo:v0.126.0-663380dd60a2' locally
docker: Error response from daemon: manifest for gcr.io/k8s-staging-sig-docs/k8s-website-hugo:v0.126.0-663380dd60a2 not found: manifest unknown: Failed to fetch "v0.126.0-663380dd60a2" from request "/v2/k8s-staging-sig-docs/k8s-website-hugo/manifests/v0.126.0-663380dd60a2".
I've messaged you @PushkarJ about how to preview the site with a different Hugo version.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
I think this'd be a really nice idea. /remove-lifecycle stale
Any takers?
@sftim Do we have any example for this so far? I could look into it if we have some example how it is done
We're not using this functionality as far as I know. Not yet.
/triage accepted
@xmudrii if you'd like to work on this, or to introduce someone with an interest, I reckon SIG Docs can coach them. I may well have capacity in the 2nd part of November (2024).
/assign
/priority important-longterm
IMO