Updates the install docs for the v2.34.0 release, branched off the latest `main`. Supersedes #25995: same release-docs update, but cut from current `main` and with every "Latest Release" link refreshed. The automated PR carried stale patch links and a `vv2.34.0` typo. ## Changes - `docs/install/releases/index.md`: regenerate the release calendar. 2.34 → Mainline, 2.33 → Stable, and every "Latest Release" link points to the current patch per minor (`2.24.6, 2.29.16, 2.30.9, 2.31.14, 2.32.5, 2.33.6, 2.34.0`). - `docs/install/rancher.md`: version selector → Mainline `2.34.0`, Stable `2.33.6`. - `docs/install/kubernetes.md`: Helm `--version` → Mainline `2.34.0`, Stable `2.33.6` (chart + OCI), matching the Rancher guide. Addresses the review feedback on #25995: the `vv2.34.0` typo, bumping Stable to `2.33.6`, and keeping the Kubernetes guide in sync with Rancher. <details> <summary>Notes for reviewers</summary> - Verified with `markdownlint-cli2` (0 errors) and `markdown-table-formatter --check` (no reformatting needed). - The calendar was regenerated via `scripts/update-release-calendar.sh`. That script's `get_latest_patch` does not exclude prerelease tags, so it selected `v2.34.0-rc.0` over `v2.34.0`; that row was corrected by hand. A follow-up fix to the script would prevent this recurring. - The linkspector 404 on `coder.com/changelog/coder-2-34` is expected for a fresh release; that page publishes alongside the release. </details> --- *Generated by Coder Agents on behalf of @f0ssel.*
5.1 KiB
Deploy Coder on Rancher
You can deploy Coder on Rancher as a Workload.
Requirements
- SUSE Rancher Manager running Kubernetes (K8s) 1.19+ with SUSE Rancher Prime distribution (Rancher Manager 2.10+)
- Helm 3.5+ installed
- Workload Kubernetes cluster for Coder
Overview
Installing Coder on Rancher involves four key steps:
- Create a namespace for Coder
- Set up PostgreSQL
- Create a database connection secret
- Install the Coder application via Rancher UI
Create a namespace
Create a namespace for the Coder control plane. In this tutorial, we call it coder:
kubectl create namespace coder
Set up PostgreSQL
Coder requires a PostgreSQL database to store deployment data. We recommend that you use a managed PostgreSQL service, but you can use an in-cluster PostgreSQL service for non-production deployments:
Managed PostgreSQL (Recommended)
For production deployments, we recommend using a managed PostgreSQL service:
- Google Cloud SQL
- AWS RDS for PostgreSQL
- Azure Database for PostgreSQL
- DigitalOcean Managed PostgreSQL
Ensure that your PostgreSQL service:
- Is running and accessible from your cluster
- Is in the same network/project as your cluster
- Has proper credentials and a database created for Coder
In-Cluster PostgreSQL (Development/PoC)
For proof-of-concept deployments, you can use Bitnami Helm chart to install PostgreSQL in your Kubernetes cluster:
helm repo add bitnami https://charts.bitnami.com/bitnami
helm install coder-db bitnami/postgresql \
--set image.repository=bitnamilegacy/postgresql \
--namespace coder \
--set auth.username=coder \
--set auth.password=coder \
--set auth.database=coder \
--set persistence.size=10Gi
After installation, the cluster-internal database URL will be:
postgres://coder:coder@coder-db-postgresql.coder.svc.cluster.local:5432/coder?sslmode=disable
For more advanced PostgreSQL management, consider using the Postgres operator.
Create the database connection secret
Create a Kubernetes secret with your PostgreSQL connection URL:
kubectl create secret generic coder-db-url -n coder \
--from-literal=url="postgres://coder:coder@coder-db-postgresql.coder.svc.cluster.local:5432/coder?sslmode=disable"
Important
If you're using a managed PostgreSQL service, replace the connection URL with your specific database credentials.
Install Coder through the Rancher UI
-
In the Rancher Manager console, select your target Kubernetes cluster for Coder.
-
Navigate to Apps > Charts
-
From the dropdown menu, select Partners and search for
Coder -
Select Coder, then Install
-
Select the
codernamespace you created earlier and check Customize Helm options before install.Select Next
-
On the configuration screen, select Edit YAML and enter your Coder configuration settings:
Example values.yaml configuration
coder: # Environment variables for Coder env: - name: CODER_PG_CONNECTION_URL valueFrom: secretKeyRef: name: coder-db-url key: url # For production, uncomment and set your access URL # - name: CODER_ACCESS_URL # value: "https://coder.example.com" # For TLS configuration (uncomment if needed) #tls: # secretNames: # - my-tls-secret-nameFor available configuration options, refer to the Helm chart documentation or values.yaml file.
-
Select a Coder version:
- Mainline:
2.34.0 - Stable:
2.33.6
Learn more about release channels in the Releases documentation.
- Mainline:
-
Select Next when your configuration is complete.
-
On the Supply additional deployment options screen:
- Accept the default settings
- Select Install
-
A Helm install output shell will be displayed and indicates the installation status.
Manage your Rancher Coder deployment
To update or manage your Coder deployment later:
- Navigate to Apps > Installed Apps in the Rancher UI.
- Find and select Coder.
- Use the options in the ⋮ menu for upgrade, rollback, or other operations.
