-
Notifications
You must be signed in to change notification settings - Fork 126
Rework documents for unsupported features #4470
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
base: milestone-28-azure-cloud
Are you sure you want to change the base?
Rework documents for unsupported features #4470
Conversation
Allow 10 minutes from last push for the staging site to build. If the link doesn't work, try using incognito mode instead. For internal reviewers, check web-documentation repo actions for staging build status. Link to build for this PR: http://docs-dev.timescale.com/docs-502-rework-documents-for-unsupported-features |
<Tabs label="Tiger Cloud on AWS and Azure" persistKey="tiger-platform-clouds"> | ||
|
||
<Tab title="Tiger Cloud on AWS" label="aws-cloud"> |
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 wasn't sure what that feature means, but when I read it turned out it's a Transit Gateway peering. It looks strange how it's called and that it's in the integrations section. It's in general, not related to Azure support.
integrations/microsoft-azure.md
Outdated
|
||
<Tab title="Tiger Cloud on Azure" label="azure-cloud"> | ||
|
||
<NotSupportedAzure /> |
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 don't understand it. Do we not support Azure on Microsoft Azure?
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.
There are four pages hinging on AWS Transit Gateway support, this one including. There is no TGW support on Azure Tiger Cloud. I admit this is tricky and needs to be revisited for clarity.
|
||
<Tab title="Tiger Cloud on Azure" label="azure-cloud"> | ||
|
||
$CLOUD_LONG stores your data in high-performance storage optimized for frequent querying. Based on [AWS EBS gp3][aws-gp3], the high-performance storage provides you with up to 16 TB and 16,000 IOPS. Its [$HYPERCORE row-columnar storage engine][hypercore], designed specifically for real-time analytics, enables you to compress your data by up to 98%, while improving performance. |
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.
With the recent changes in gp3, which now supports 64000 IOPS and 64TB, we need @rahilsondhi to reconsider external communications about it
…into 502-rework-documents-for-unsupported-features # Conflicts: # use-timescale/data-tiering/index.md # use-timescale/security/overview.md
No description provided.