Website: Kubernetes v1.19 - Doc Reference Page has mismatch links

Created on 10 Dec 2020 · 13Comments · Source: kubernetes/website

Problem :
In the v1.19 version of the Kubernetes site - https://v1-19.docs.kubernetes.io/docs/reference/, we are seeing the link for Kubernetes API - https://v1-19.docs.kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/

Steps to Reproduce :

Navigate to the URL: https://kubernetes.io/ and in the versions choose v1.19
2.It will be redirected to https://v1-19.docs.kubernetes.io/
3.Documentation -> reference, under API Reference section we are able to spot a wrong link for v1.20 _Kubernetes API Reference v1.20_

Solution :
https://v1-19.docs.kubernetes.io/docs/reference/generated/kubernetes-api/v1.19/ is the correct Kubernetes API Reference for v1.19 and the link has to be re-titled as Kubernetes API Reference v1.19

Note: As the further older doc versions are not maintained, not sure if it has to be fixed in those as well.

kinbug prioritimportant-soon triagaccepted

Source

raghvenders

👀1

All 13 comments

/triage accepted
/kind bug

savitharaghunathan on 10 Dec 2020

/priority important-soon
@annajung FYI

sftim on 11 Dec 2020

👍1

This looks like a metadata bug, but I'm not exactly sure where the fix is (as I haven't yet investigated)

sftim on 11 Dec 2020

The behavior seen here (linking to the current API reference) has come from https://github.com/kubernetes/website/pull/18837

sftim on 11 Dec 2020

👀

kbhawkey on 11 Dec 2020

The config.toml in the release-1.19 branch should set latest to 1.19.
The shortcode uses, {{ site.Params.latest }} and this variable is set to 1.20.

kbhawkey on 11 Dec 2020

I can fix this.

kbhawkey on 11 Dec 2020

👍1

/assign

kbhawkey on 11 Dec 2020

The 1.18, 1.17 branches appear to depend on the latest parameter as well.

kbhawkey on 11 Dec 2020

Hi @raghvenders .
What do you think about closing this issue?

kbhawkey on 15 Dec 2020

Feel free to reopen if the issue is still there.
/close

tengqm on 17 Dec 2020

@tengqm: Closing this issue.

In response to this:

Feel free to reopen if the issue is still there.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.