Add deprecation warnings for multi-node (timescale#2855)

iroussos · web-flow · commit b047fe7d3821 · 2023-11-29T14:12:50.000+02:00
diff --git a/_partials/_multi-node-deprecation.md b/_partials/_multi-node-deprecation.md
@@ -0,0 +1,7 @@
+<Highlight type="warning">
+Multi-node support has been deprecated with TimescaleDB 2.13. This is the last version that includes multi-node support and it supports multi-node installations with PostgreSQL versions 13, 14, and 15.
+
+Learn more about it [here][multi-node-deprecation].
+</Highlight>
+
+[multi-node-deprecation]: https://github.com/timescale/timescaledb/blob/main/docs/MultiNodeDeprecation.md
diff --git a/self-hosted/distributed-hypertables/about-distributed-hypertables.md b/self-hosted/distributed-hypertables/about-distributed-hypertables.md
@@ -5,6 +5,10 @@ products: [self_hosted]
 keywords: [distributed hypertables, multi-node]
 ---
 
+import MultiNodeDeprecation from "versionContent/_partials/_multi-node-deprecation.mdx";
+
+<MultiNodeDeprecation />
+
 # About distributed hypertables
 
 Distributed hypertables are hypertables that span multiple nodes. With
diff --git a/self-hosted/distributed-hypertables/alter-drop-distributed-hypertables.md b/self-hosted/distributed-hypertables/alter-drop-distributed-hypertables.md
@@ -6,6 +6,10 @@ keywords: [distributed hypertables, alter, delete]
 tags: [change, delete]
 ---
 
+import MultiNodeDeprecation from "versionContent/_partials/_multi-node-deprecation.mdx";
+
+<MultiNodeDeprecation />
+
 # Alter and drop distributed hypertables
 
 You can alter and drop distributed hypertables in the same way as standard
diff --git a/self-hosted/distributed-hypertables/create-distributed-hypertables.md b/self-hosted/distributed-hypertables/create-distributed-hypertables.md
@@ -5,6 +5,10 @@ products: [self_hosted]
 keywords: [distributed hypertables, multi-node, create]
 ---
 
+import MultiNodeDeprecation from "versionContent/_partials/_multi-node-deprecation.mdx";
+
+<MultiNodeDeprecation />
+
 # Create distributed hypertables
 
 If you have a [multi-node environment][multi-node], you can create a distributed
diff --git a/self-hosted/distributed-hypertables/foreign-keys.md b/self-hosted/distributed-hypertables/foreign-keys.md
@@ -6,6 +6,10 @@ keywords: [distributed hypertable, foreign keys]
 tags: [constraints]
 ---
 
+import MultiNodeDeprecation from "versionContent/_partials/_multi-node-deprecation.mdx";
+
+<MultiNodeDeprecation />
+
 # Create foreign keys in a distributed hypertable
 
 Tables and values referenced by a distributed hypertable must be present on the
diff --git a/self-hosted/distributed-hypertables/index.md b/self-hosted/distributed-hypertables/index.md
@@ -5,6 +5,10 @@ products: [self_hosted]
 keywords: [distributed hypertables, multi-node]
 ---
 
+import MultiNodeDeprecation from "versionContent/_partials/_multi-node-deprecation.mdx";
+
+<MultiNodeDeprecation />
+
 # Distributed hypertables
 
 Distributed hypertables are hypertables that span multiple nodes. With
diff --git a/self-hosted/distributed-hypertables/insert.md b/self-hosted/distributed-hypertables/insert.md
@@ -6,6 +6,10 @@ keywords: [write, distributed hypertables]
 tags: [ingest, insert]
 ---
 
+import MultiNodeDeprecation from "versionContent/_partials/_multi-node-deprecation.mdx";
+
+<MultiNodeDeprecation />
+
 # Insert data
 
 You can insert data into a distributed hypertable with an `INSERT` statement.
diff --git a/self-hosted/distributed-hypertables/query.md b/self-hosted/distributed-hypertables/query.md
@@ -5,6 +5,10 @@ products: [self_hosted]
 keywords: [distributed hypertables, multi-node, queries]
 ---
 
+import MultiNodeDeprecation from "versionContent/_partials/_multi-node-deprecation.mdx";
+
+<MultiNodeDeprecation />
+
 # Query data in distributed hypertables
 
 You can query a distributed hypertable just as you would query a standard
diff --git a/self-hosted/distributed-hypertables/triggers.md b/self-hosted/distributed-hypertables/triggers.md
@@ -5,6 +5,10 @@ products: [self_hosted]
 keywords: [distributed hypertables, triggers, multi-node]
 ---
 
+import MultiNodeDeprecation from "versionContent/_partials/_multi-node-deprecation.mdx";
+
+<MultiNodeDeprecation />
+
 # Use triggers on distributed hypertables
 
 Triggers on distributed hypertables work in much the same way as triggers on
diff --git a/self-hosted/multinode-timescaledb/about-multinode.md b/self-hosted/multinode-timescaledb/about-multinode.md
@@ -5,6 +5,10 @@ products: [self_hosted]
 keywords: [multi-node]
 ---
 
+import MultiNodeDeprecation from "versionContent/_partials/_multi-node-deprecation.mdx";
+
+<MultiNodeDeprecation />
+
 # About multi-node
 
 If you have a larger petabyte-scale workload, you might need more than
diff --git a/self-hosted/multinode-timescaledb/index.md b/self-hosted/multinode-timescaledb/index.md
@@ -5,6 +5,10 @@ products: [self_hosted]
 keywords: [multi-node, scaling]
 ---
 
+import MultiNodeDeprecation from "versionContent/_partials/_multi-node-deprecation.mdx";
+
+<MultiNodeDeprecation />
+
 # Multi-node
 
 If you have a larger workload, you might need more than one TimescaleDB
@@ -28,4 +32,4 @@ giving you faster data ingest, and more responsive and efficient queries.
 [multi-node-grow-shrink]: /self-hosted/:currentVersion:/multinode-timescaledb/multinode-grow-shrink/
 [multi-node-ha]: /self-hosted/:currentVersion:/multinode-timescaledb/multinode-ha/
 [multi-node-maintenance]: /self-hosted/:currentVersion:/multinode-timescaledb/multinode-maintenance/
-[setup-selfhosted]: /self-hosted/:currentVersion:/multinode-timescaledb/multinode-setup/
+[setup-selfhosted]: /self-hosted/:currentVersion:/multinode-timescaledb/multinode-setup/
diff --git a/self-hosted/multinode-timescaledb/multinode-administration.md b/self-hosted/multinode-timescaledb/multinode-administration.md
@@ -6,6 +6,10 @@ keywords: [multi-node, admin]
 tags: [manage]
 ---
 
+import MultiNodeDeprecation from "versionContent/_partials/_multi-node-deprecation.mdx";
+
+<MultiNodeDeprecation />
+
 # Multi-node administration
 
 Multi-node TimescaleDB allows you to administer your cluster directly
diff --git a/self-hosted/multinode-timescaledb/multinode-auth.md b/self-hosted/multinode-timescaledb/multinode-auth.md
@@ -6,6 +6,10 @@ keywords: [multi-node, authenticate]
 tags: [admin]
 ---
 
+import MultiNodeDeprecation from "versionContent/_partials/_multi-node-deprecation.mdx";
+
+<MultiNodeDeprecation />
+
 # Multi-node authentication
 
 When you have your instances set up, you need to configure them to accept
diff --git a/self-hosted/multinode-timescaledb/multinode-config.md b/self-hosted/multinode-timescaledb/multinode-config.md
@@ -5,6 +5,10 @@ products: [self_hosted]
 keywords: [configuration, settings, multi-node]
 ---
 
+import MultiNodeDeprecation from "versionContent/_partials/_multi-node-deprecation.mdx";
+
+<MultiNodeDeprecation />
+
 # Multi-node configuration
 
 In addition to the
diff --git a/self-hosted/multinode-timescaledb/multinode-grow-shrink.md b/self-hosted/multinode-timescaledb/multinode-grow-shrink.md
@@ -6,6 +6,10 @@ keywords: [multi-node, data nodes]
 tags: [add, remove]
 ---
 
+import MultiNodeDeprecation from "versionContent/_partials/_multi-node-deprecation.mdx";
+
+<MultiNodeDeprecation />
+
 # Grow and shrink multi-node
 
 When you are working within a multi-node environment, you might discover that
diff --git a/self-hosted/multinode-timescaledb/multinode-ha.md b/self-hosted/multinode-timescaledb/multinode-ha.md
@@ -5,6 +5,10 @@ products: [self_hosted]
 keywords: [multi-node, high availability]
 ---
 
+import MultiNodeDeprecation from "versionContent/_partials/_multi-node-deprecation.mdx";
+
+<MultiNodeDeprecation />
+
 # High availability with multi-node
 
 A multi-node installation of TimescaleDB can be made highly available
diff --git a/self-hosted/multinode-timescaledb/multinode-maintenance.md b/self-hosted/multinode-timescaledb/multinode-maintenance.md
@@ -6,6 +6,10 @@ keywords: [multi-node, maintenance]
 tags: [manage]
 ---
 
+import MultiNodeDeprecation from "versionContent/_partials/_multi-node-deprecation.mdx";
+
+<MultiNodeDeprecation />
+
 # Multi-node maintenance tasks
 
 Various maintenance activities need to be carried out for effective
diff --git a/self-hosted/multinode-timescaledb/multinode-setup.md b/self-hosted/multinode-timescaledb/multinode-setup.md
@@ -5,6 +5,10 @@ products: [self_hosted]
 keywords: [multi-node, self-hosted]
 ---
 
+import MultiNodeDeprecation from "versionContent/_partials/_multi-node-deprecation.mdx";
+
+<MultiNodeDeprecation />
+
 # Set up multi-node on self-hosted TimescaleDB
 
 To set up multi-node on a self-hosted TimescaleDB instance, you need:
