Skip to content

chore: add usage note for Azure users #673

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 19, 2021
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion guides/admin/timescale-migration.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,14 @@ At the end of your evaluation period, you may need to migrate the data from the
built-in database to an out-of-cluster PostgreSQL database for production use.
This article will walk you through the process of doing so.

> You must be a cluster admin for your Kubernetes cluster.
## Requirements

- You must be a cluster admin for your Kubernetes cluster.

- **Azure database users**: if you're using Azure Database for PostgreSQL, note
that Coder only works with Single Server; the Flexible Server (Preview) and
Hyperscale (Citus) options do _not_ support the TimescaleDB extension
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@khorne3 @mterhar Wait, I didn't realize we were using Timescale features still, my understanding is that we're using stock PostgreSQL completely now. How did we run into this issue?

cc @coadler @ericpaulsen

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We no longer require any Timescale features! Any of these should work

required.

## Migration Steps

Expand Down