CTRT refactor for Kubernetes executor page part 1
What does this MR do?
CTRT refactor for Kubernetes page. This MR includes edits up to and including the section ## Using the cache with the Kubernetes executor
.
- Re-organized a configuration table so that the parameter settings are alphebetized.
- Updated heading names.
- Parsed language to make more concise and less passive.
- Created
Configure runner permissions
section to separate content from theOverwrite Kubernetes namespaces
because it describes a separate type of procedure.
Before: https://docs.gitlab.com/runner/executors/kubernetes.html#the-kubernetes-executor-for-gitlab-runner
After: https://main-runner-3928.docs.gitlab-review.app/runner/executors/kubernetes.html
Related issues
technical-writing#749 (closed)
Author's checklist
-
Optional. Consider taking the GitLab Technical Writing Fundamentals course. -
Follow the: -
If you're adding or changing the main heading of the page (H1), ensure that the product tier badge is added. -
If you are a GitLab team member, request a review based on: - The documentation page's metadata.
- The associated Technical Writer.
If you are a GitLab team member and only adding documentation, do not add any of the following labels:
~"frontend"
~"backend"
~"type::bug"
~"database"
These labels cause the MR to be added to code verification QA issues.
Reviewer's 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 you aren't sure which tech writer to ask, use roulette or ask in the #docs Slack channel.
-
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. -
Ensure a release milestone is set. - 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.