## Summary Add YAML front matter to the remaining published documentation pages so all published pages expose a title through front matter. ## Changes - Add front matter to the 13 published pages that were missing it. - Preserve the page titles and feature states in the manifest. - Remove duplicate H1 headings where the front matter supplies the page title. ## Testing - `pnpm check-docs` passed. - Repository pre-commit checks passed. - Verified all 439 published manifest route entries have YAML front matter. Depends on #30109. Refs DOCS-1124. This pull request was generated by Coder Agents.
2.1 KiB
title
| title |
|---|
| Install the control plane |
The pages in this section are alternatives, not sequential steps. Choose the one that matches the platform your team already operates, or intends to operate, then follow it through to the end.
Choose a platform
| Platform | Best suited to |
|---|---|
| Kubernetes | Production deployments, including high availability with multiple replicas |
| Rancher | Kubernetes clusters your team already manages through Rancher |
| OpenShift | Red Hat OpenShift clusters, which need specific security context settings |
| Docker | A single machine, such as a proof of concept or a small team deployment |
| RPM (RHEL family) | A single Red Hat Enterprise Linux host, or another RHEL-family distribution |
| Cloud providers | A virtual machine on AWS, Google Cloud, or Azure, or a marketplace listing |
| Community install methods | Platforms Coder doesn't package, where a community-contributed method exists |
If your platform choice is still open, size the deployment first in Plan your deployment. The Coder Validated Architecture reference designs assume Kubernetes, which is the recommended platform for deployments that others depend on.
Before you move on
At the end of this phase you should be able to reach the Coder access URL, sign in as the first administrator, and see the deployment reported as healthy. If you prepared a license and an identity provider application in Prepare prerequisites, apply them now so that the deployment you validate is the one you intend to run.
Next: Validate your deployment.