-
Notifications
You must be signed in to change notification settings - Fork 141
aligned capitalization for Elastic Clusters #310
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
Conversation
removed irrlelevant region question clarified extensions info added question regarding public preview to GA transition added info for pgbouncer and re: port 7432 CMK not available from portal confirmed Entra is working
|
@JaredMSFT : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 7c8e8ec: ✅ Validation status: passed
For more details, please refer to the build report. |
PRMerger Results
|
| metadata: | ||
| title: Limitations of elastic clusters (preview) | ||
| description: "Learn about existing limitations of elastic clusters with Azure Database for PostgreSQL Flexible server during public preview." | ||
| title: Limitations of Elastic Clusters (preview) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
elastic clusters are a feature hence lowercase
| title: Limitations of elastic clusters (preview) | ||
| description: "Learn about existing limitations of elastic clusters with Azure Database for PostgreSQL Flexible server during public preview." | ||
| title: Limitations of Elastic Clusters (preview) | ||
| description: "Learn about existing limitations of Elastic Clusters with Azure Database for PostgreSQL Flexible server during public preview." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
as above
| ms.custom: references_regions | ||
|
|
||
| title: "Frequently asked questions about elastic clusters (preview)" | ||
| title: "Frequently asked questions about Elastic Clusters (preview)" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lowercase, plus all other instances in the doc that are not beginning of sentence.
| - postgis_topology | ||
| - TimescaleDB | ||
| - question: Which extensions are available for Elastic Clusters? | ||
| answer: Elastic Clusters are compatible with many other powerful extensions, however, it's important to review the list of supported extensions along with any specific release notes. You can find the list of supported extensions under the [Citus GitHub repo](https://github.com/citusdata/citus/blob/main/EXTENSION_COMPATIBILITY.md). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do without marketing speak like "powerful extensions". I would say elastic cluster is compatible with the majority of PostgreSQL extensions. For a comprehensive list with support details please refer to the [extension compatibility matrix] in the Citus GitHub repository.
| answer: Migrations to/from Elastic Clusters can be done with pg_dump, pg_restore, and pgcopydb. Any other tool working with standard PostgreSQL should work. | ||
|
|
||
| - question: Can I convert my existing Public Preview instance to General Availability (GA) Elastic Clusters? | ||
| answer: Public Preview clusters cannot be converted/promoted to GA clusters. Migration to GA Elastic Clusters can be made following the migration methods described above. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is too soft and hiding the intent. We want people to realize they will need to re-create their clusters on GA. This is a scream test.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will use the banner text.
| - question: Can I use PgBouncer for connection pooling with elastic clusters? | ||
| answer: Yes, you can use PgBouncer with elastic clusters. Port 6432 should be used for schema and node management operations, while port 8432 is load-balanced to PgBouncer instances running across all nodes in the cluster. | ||
| - question: Can I use PgBouncer for connection pooling with Elastic Clusters? | ||
| answer: Public Preview does not currently support PgBouncer with Elastic Clusters. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What happened here? We can use PgBouncer with elastic clusters. The removed text was correct.
| - question: Can I use PgBouncer for connection pooling with Elastic Clusters? | ||
| answer: Public Preview does not currently support PgBouncer with Elastic Clusters. | ||
|
|
||
| - question: Which ports are used for Elastic Clusters? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Where did this came from?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is based on info from our docs (https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/concepts-elastic-clusters#architecture)
I have removed for now, but I thought it would be a common question for users when seeking to understand how the elastic cluster ports operate.
| answer: Public Preview does not currently support PgBouncer with Elastic Clusters. | ||
|
|
||
| - question: Which ports are used for Elastic Clusters? | ||
| answer: Port 7432 is used to balance incoming client connections across all nodes in the Citus cluster, including both coordinator and worker nodes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This doesn't answer the question. Lists one port out of at least 4 used by elastic clusters. Also describes how the load balancer works.
| - question: Can I use replicas with elastic clusters? | ||
|
|
||
| - question: Can I use replicas with Elastic Clusters? | ||
| answer: Currently, replicas aren't supported during the preview. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Replicas are supported now, at least single replicas but multi replicas are not, right?
| - question: Can I use Microsoft Entra ID authentication with elastic clusters? | ||
| answer: Currently, Microsoft Entra ID authentication isn't supported during the preview. | ||
| - question: Can I use Microsoft Entra ID authentication with Elastic Clusters? | ||
| answer: Yes! Microsoft Entra ID authentication is currently supported and follows the same principles found in Flexible Server. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We are flexible server. I would just say "Yes, refer to [name of documentation] for details" and just link to the flex docs.
|
#label:"aq-pr-triaged" |
incorporated feedback comments.
|
Learn Build status updates of commit d382591: ✅ Validation status: passed
For more details, please refer to the build report. |
PRMerger Results
|
|
Learn Build status updates of commit 71c76f6: ✅ Validation status: passed
For more details, please refer to the build report. |
PRMerger Results
|
|
#sign-off |
|
@JaredMSFT and @mulander Microsoft email addresses aren't allowed in Learn content. Can you remove or rewrite the last sentence at line 68 to comply with this guidance? (Unauthorized content, item 8). #hold-off |
@ttorble the linked guide is not found (404). Can you point us at the correct resource? |
|
Learn Build status updates of commit ccd9798: ✅ Validation status: passed
For more details, please refer to the build report. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left few comments.
| - question: Elastic clusters aren't available in the region I need, what can I do? | ||
| answer: | | ||
| We're enabling other regions shortly, if you're interested in specific regions fill out [this form](https://aka.ms/preview-pg-citus). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should not direct them to a form, there are concerns around PII... Rather open a support case with Capacity management type thing, Aka this si the "same" as Flex being available in any region no different
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR removes that section completely, but point taken and noted.
articles/postgresql/flexible-server/concepts-elastic-clusters-limitations.yml
Show resolved
Hide resolved
articles/postgresql/flexible-server/concepts-elastic-clusters-limitations.yml
Outdated
Show resolved
Hide resolved
articles/postgresql/flexible-server/concepts-elastic-clusters-limitations.yml
Outdated
Show resolved
Hide resolved
articles/postgresql/flexible-server/concepts-elastic-clusters-limitations.yml
Outdated
Show resolved
Hide resolved
articles/postgresql/flexible-server/concepts-elastic-clusters-limitations.yml
Outdated
Show resolved
Hide resolved
articles/postgresql/flexible-server/concepts-elastic-clusters-limitations.yml
Outdated
Show resolved
Hide resolved
articles/postgresql/flexible-server/concepts-elastic-clusters-limitations.yml
Outdated
Show resolved
Hide resolved
articles/postgresql/flexible-server/concepts-elastic-clusters-limitations.yml
Outdated
Show resolved
Hide resolved
articles/postgresql/flexible-server/concepts-elastic-clusters-limitations.yml
Outdated
Show resolved
Hide resolved
|
Learn Build status updates of commit b1e078f: ✅ Validation status: passed
For more details, please refer to the build report. |
PRMerger Results
|
Make sure you're signed in and the link should work. |
articles/postgresql/flexible-server/concepts-elastic-clusters-limitations.yml
Outdated
Show resolved
Hide resolved
articles/postgresql/flexible-server/concepts-elastic-clusters-limitations.yml
Outdated
Show resolved
Hide resolved
| answer: Migrations to/from elastic clusters can be done with pg_dump, pg_restore, and pgcopydb. Any other tool working with standard PostgreSQL should work. | ||
|
|
||
| - question: Can I convert my existing Public Preview instance to General Availability (GA) elastic clusters? | ||
| answer: If you have created any elastic clusters during the Public Preview phase, you are required to re-create them once the feature becomes Generally Available. If this raises concerns, or if you need help determining whether your server meets the necessary requirements, please contact us by going to the Azure portal, selecting your Azure Postgres resource, and following the instructions in the banner. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if it's not better to ask them to raise a support request? The banner doesn't show in all cases.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm concerned raising a support incident will cause more complexity and hassle for the customer and for the customer support org. At least the banner instructs them to contact us directly. Can we determine why the banner does not show in all relevant cases?
articles/postgresql/flexible-server/concepts-elastic-clusters-limitations.yml
Outdated
Show resolved
Hide resolved
articles/postgresql/flexible-server/concepts-elastic-clusters-limitations.yml
Outdated
Show resolved
Hide resolved
articles/postgresql/flexible-server/concepts-elastic-clusters-limitations.yml
Outdated
Show resolved
Hide resolved
articles/postgresql/flexible-server/concepts-elastic-clusters-limitations.yml
Outdated
Show resolved
Hide resolved
articles/postgresql/flexible-server/concepts-elastic-clusters-limitations.yml
Outdated
Show resolved
Hide resolved
|
Learn Build status updates of commit 537fc5b: ✅ Validation status: passed
For more details, please refer to the build report. |
PRMerger Results
|
|
#sign-off |
|
Learn Build status updates of commit 3c23e37: ✅ Validation status: passed
For more details, please refer to the build report. |
PRMerger Results
|
|
@JaredMSFT and @mulander Updates to this article contain future promises, which are not allowed in Learn content. articles/postgresql/flexible-server/concepts-elastic-clusters-limitations.yml
Note that contributor guidance has moved to https://learn.microsoft.com/help/ Thanks |
|
You typed hold-off, but the PR wasn't signed off, so nothing was changed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR updates the FAQ documentation for Azure Database for PostgreSQL Elastic Clusters to reflect current capabilities and prepare for the transition from public preview to general availability (GA). The changes include removing outdated questions, clarifying feature availability, and providing more detailed information about supported functionality.
Key changes:
- Removed irrelevant region availability question and clarified extension compatibility
- Added information about the public preview to GA transition requirements
- Updated networking, authentication, and performance capabilities to reflect current state
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
articles/postgresql/flexible-server/concepts-elastic-clusters-limitations.yml
Outdated
Show resolved
Hide resolved
|
Learn Build status updates of commit 533fcf7: ✅ Validation status: passed
For more details, please refer to the build report. |
PRMerger Results
|
|
Learn Build status updates of commit 12c2430: ✅ Validation status: passed
For more details, please refer to the build report. |
PRMerger Results
|
|
@mulander - Would you add a comment to indicate what action to take on this PR? Thanks! |
removed irrlelevant region question
clarified extensions info
added question regarding public preview to GA transition
added info for pgbouncer and re: port 7432
CMK not available from portal
confirmed Entra is working