Fix broken links

[remyleone]

This is a Bug Report

Here are some pages with broken links (saved as a CSV format)

Problem:

Some links on the website are broken

Proposed Solution:

Fix the link to valid ones

Page to Update:

https://github.com/kubernetes/website/files/4262612/kubernetes.io_internal_broken_links_20200227.txt

[remyleone]

/help
/good-first-issue

[k8s-ci-robot]

@remyleone:
This request has been marked as suitable for new contributors.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

/help
/good-first-issue

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.

[sftim]

https://github.com/kubernetes/website/files/4262612/kubernetes.io_internal_broken_links_20200227.txt is comma-separated, so you can open it in a tool like Microsoft Excel, Google Sheets, or OpenOffice Calc.

[sftim]

/kind cleanup

[sftim]

Fixing every broken link there is a lot of work @remyleone
Is this task the right side size for the “good first issue” label?

[tanjunchen]

I think it is ok label “good first issue”
+1

[kbhawkey]

Is it essential to include links from previous versions of the docs (snapshots)?
How about focusing only on link errors in 1.17?
Note: Do you want to correct links before (or during) a release?

[IanColdwater]

yeah sure, why not

/assign

[sftim]

How about focusing only on link errors in 1.17?

That sounds like a good place to start. Thinking about how I might handle a similar challenge in a work context, I would consider splitting the issue once the link errors in master had been dealt with.

[fejta-bot]

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

[fejta-bot]

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

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

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

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/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.