Issue with k8s.io/docs/reference/kubectl/generated/kubectl_drain/ - Links are weird

[szilard-nemeth]

In the beginning of the Synopsis, quoting:

Drain node in preparation for maintenance.
The given node will be marked unschedulable to prevent new pods from arriving. 'drain' evicts the pods if the API server supports https://kubernetes.io/docs/concepts/workloads/pods/disruptions/ eviction https://kubernetes.io/docs/concepts/workloads/pods/disruptions/ .

I don't think those 2 links should look like this.
Thanks

[k8s-ci-robot]

This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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-sigs/prow repository.

[utkarsh-singh1]

Thanks for the report @szilard-nemeth, there seems to be 2 links pointing to the same location.

[utkarsh-singh1]

Since both the mentioned page is auto-generated page it could only be fixed in the kubernetes/kubernetes repository.

/language en

[sftim]

Since both the mentioned page is auto-generated page it could only be fixed in the kubernetes/kubernetes repository.

We could also fix the code that generates the docs. This calls for a contributor skilled in Golang coding; we only have a few folk in this SIG with an interest in Golang.
If anyone wants to learn more, ask in #sig-contribex on Kubernetes Slack. The Kubernetes project overall has a large number of contributors who can write in Go.

[Aaina26]

Hi I would like to try and fix this...assigning myself
/assign

[sftim]

@Aaina26 the code to revise is in https://github.com/kubernetes-sigs/reference-docs/tree/master/gen-kubectldocs

[Maalvi14]

Hi I have experience in Golang and could help @Aaina26 on this issue
/assign

[sftim]

@Maalvi14 please considering starting a thread in Kubernetes' Slack workspace around this work. We'd love to support you and @Aaina26 on this.