Skip to content

Draft: Docs: Clusters features reference doc

Marcia Ramos requested to merge docs-clusters-reference-tables into master

What does this MR do?

  • Documents the availability of cluster-related features through reference tables.
  • Closes #339899.
  • Related to: #342708 (closed).

Review app: http://main-ee-71315.178.62.207.141.nip.io/ee/user/infrastructure/clusters/cluster_features_reference.html

VERSION 1 VERSION 2 VERSION 3
version1 version2 version3
candidate14.5

Examples:

  • Can I use Auto DevOps with a cluster connected through the Agent? (ref)

Author's checklist

My checklist:

  • Self-review
  • Fix links
  • Link from other docs
  • Open MR to add to the global nav

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 like Default behavior when you close an issue.
      • The headings (other than the page title) should be active. Instead of Configuring GDK, say something like Configure 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 Marcia Ramos

Merge request reports