Docs: Fixes outdated and redirecting links
What does this MR do?
As part of the monthly chores for March 2024, fix these findings from our link checker:
public/operator/installation.html:
[ ERROR ] external_links - broken reference to https://cert-manager.io/v1.6-docs: link has moved permanently to 'https://cert-manager.io/v1.6-docs/'
public/operator/security_context_constraints.html:
[ ERROR ] external_links - broken reference to https://cert-manager.io/docs/installation/supported-releases/: link has moved permanently to 'https://cert-manager.io/docs/releases/'
[ ERROR ] external_links - broken reference to https://www.openshift.com/blog/managing-sccs-in-openshift: link has moved permanently to 'https://www.redhat.com/en/blog/managing-sccs-in-openshift'
[ ERROR ] external_links - broken reference to https://www.openshift.com/blog/a-guide-to-openshift-and-uids: link has moved permanently to 'https://www.redhat.com/en/blog/a-guide-to-openshift-and-uids'
Related issues
Related to Docs project maintenance tasks, March 2024 (gitlab-org/technical-writing#1006 - closed)
Author's checklist
-
Consider taking the GitLab Technical Writing Fundamentals course -
Follow the: -
Merge Request Title and Description are up to date, accurate, and descriptive -
MR targeting the appropriate branch -
MR has a green pipeline on GitLab.com -
When ready for review, MR is labeled "~workflow::ready for review" per the Distribution MR workflow
If you are only adding documentation, do not add any of the following labels:
~"feature"
~"frontend"
~"backend"
~"bug"
~"database"
These labels cause the MR to be added to code verification QA issues.
Review checklist
Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.
-
If the content requires it, ensure the information is reviewed by a subject matter expert. - Technical writer review items:
-
Ensure docs metadata is present and up-to-date. -
Ensure the appropriate labels are added to this MR. - If relevant to this MR, ensure content topic type principles are in use, including:
-
The headings should be something you'd do a Google search for. Instead of Default behavior
, say something likeDefault behavior when you close an issue
. -
The headings (other than the page title) should be active. Instead of Configuring GDK
, say something likeConfigure GDK
. -
Any task steps should be written as a numbered list. - If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
-
-
-
Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review. -
Ensure a release milestone is set.
Edited by Mitchell Nielsen