gitaly docs: Remove cgroups

We currently have a bug in the cgroups implementation which makes it unusable. It's still behind a feature flag anyways, so it's better to remove the public facing docs for now until 15.1 when it's ready to use.

assigned to @jcaigitlab

requested review from @eread

Suggested Reviewers (beta)

The individuals below may be good candidates to participate in the review based on various factors.

You can use slash commands in comments to quickly assign /assign_reviewer @user1.

Suggested Reviewers
@rdickenson, @aqualls, @marcel.amirault, @smcgivern, @rymai

If you do not believe these suggestions are useful, please apply the label Bad Suggested Reviewer. You can also provide feedback for this feature on this issue: https://gitlab.com/gitlab-org/gitlab/-/issues/357923.

Automatically generated by Suggested Reviewers Bot - an experimental ML-based recommendation engine created by ~"group::applied ml".

	2 Warnings
	Please add a merge request type to this merge request.
	This merge request does not refer to an existing milestone.

	1 Message
	This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge.

If needed, you can retry the danger-review job that generated this comment.

Documentation review

The following files require a review from a technical writer:

• doc/administration/gitaly/configure_gitaly.md
• doc/administration/gitaly/monitoring.md

The review does not need to block merging this merge request. See the:

• Metadata for the *.md files that you've changed. The first few lines of each *.md file identify the stage and group most closely associated with your docs change.
• The Technical Writer assigned for that stage and group.
• Documentation workflows for information on when to assign a merge request for review.

Generated by Danger

added 1 commit

• c2d3a07a - gitaly docs: Remove cgroups

Compare with previous version

added 1 commit

• 6d739e98 - Gitaly docs: Remove cgroups

Compare with previous version

approved this merge request

merged

@eread, did you forget to run a pipeline before you merged this work? Based on our code review process, if the latest pipeline finished more than 2 hours ago, you should:

1. Ensure the merge request is not in Draft status.
2. Start a pipeline (especially important for Community contribution merge requests).
3. Set the merge request to merge when pipeline succeeds.

(Improve this message?)

mentioned in commit d78aa8e8

Thanks @jcaigitlab. When we restore it, we should also mention the feature flags explicitly.

changed milestone to %15.0

added Technical Writing devopscreate docsimprovement documentation groupgitaly labels

added workflowstaging-canary label

added workflowcanary label and removed workflowstaging-canary label

added workflowstaging label and removed workflowcanary label

added workflowproduction label and removed workflowstaging label

added releasedpublished label

added releasedcandidate label and removed releasedpublished label