Gitaly: Promote Gitaly on K8s to Beta

What does this MR do and why?

Gitaly on K8s is ready for Beta support. These docs have been published for a year now, and we feel confident in K8s as a valid deployment for Gitaly.

This MR promotes the feature to Beta whilst adding it to the Early Access Program.

References

This proposal includes more context for why we want to release Gitaly K8s in beta.

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before	After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

assigned to @jcaigitlab

@leeeee-gtlb is this enough to indicate that Gitaly on K8s is in Beta? Would we need to include something more explicit that we are not going to provide wide support for this?

marked this merge request as draft

added documentation label

	1 Message
	This merge request adds or changes documentation files and requires Technical Writing review. The review should happen before merge, but can be post-merge if the merge request is time sensitive.

Documentation review

The following files require a review from a technical writer:

• doc/administration/gitaly/kubernetes.md (Link to current live version)
• doc/policy/early_access_program/_index.md (Link to current live version)

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.

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

Generated by Danger

Proper labels assigned to this merge request. Please ignore me.

@jcaigitlab - please see the following guidance and update this merge request.

	1 Error
	Please add typebug typefeature, or typemaintenance label to this merge request.

added docs-only label

requested review from @leeeee-gtlb

requested review from @lyle

requested review from @knockfog-ext and @nick_vh

changed the description

requested review from @eread

/cc @jamesliu-gitlab @andrashorvath @fzimmer @mjwood

approved this merge request

Hi @eread ,

GitLab Bot has added the Technical Writing label because a Technical Writer has approved or merged this MR.

This message was generated automatically. Improve it or delete it.

added Technical Writing label

changed milestone to %17.10

added devopssystems groupgitaly labels

added Category:Gitaly devopsdata_access sectioninfrastructure platforms labels and removed devopssystems label

added typemaintenance label

approved this merge request

approved this merge request

approved this merge request

approved this merge request

marked this merge request as ready

resolved all threads

@jcaigitlab We have a lot of approvals now so I'll merge.

enabled automatic add to merge train when checks pass

started a merge train

merged

mentioned in commit f0dd3a66

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