add tip about operational burden

Author: Blargian

docs/deployment-guides/replication-sharding-examples/01_1_shard_2_replicas.md

@@ -19,6 +19,7 @@ import KeeperConfigExplanation from '@site/docs/deployment-guides/replication-sh
 import VerifyKeeperStatus from '@site/docs/deployment-guides/replication-sharding-examples/_snippets/_verify_keeper_using_mntr.mdx';
 import DedicatedKeeperServers from '@site/docs/deployment-guides/replication-sharding-examples/_snippets/_dedicated_keeper_servers.mdx';
 import ExampleFiles from '@site/docs/deployment-guides/replication-sharding-examples/_snippets/_working_example.mdx';
+import CloudTip from '@site/docs/deployment-guides/replication-sharding-examples/_snippets/_cloud_tip.mdx';
 
 > In this example, you'll learn how to set up a simple ClickHouse cluster which
 replicates the data. There are five servers configured. Two are used to host 
@@ -395,6 +396,8 @@ In this example, each `users.xml` file is identical for all nodes in the cluster
 
 <KeeperConfigExplanation/>
 
+<CloudTip/>
+
 ## Test the setup {#test-the-setup}
 
 Make sure that docker is running on your machine.

docs/deployment-guides/replication-sharding-examples/02_2_shards_1_replica.md

@@ -19,6 +19,7 @@ import KeeperConfigExplanation from '@site/docs/deployment-guides/replication-sh
 import VerifyKeeperStatus from '@site/docs/deployment-guides/replication-sharding-examples/_snippets/_verify_keeper_using_mntr.mdx';
 import DedicatedKeeperServers from '@site/docs/deployment-guides/replication-sharding-examples/_snippets/_dedicated_keeper_servers.mdx';
 import ExampleFiles from '@site/docs/deployment-guides/replication-sharding-examples/_snippets/_working_example.mdx';
+import CloudTip from '@site/docs/deployment-guides/replication-sharding-examples/_snippets/_cloud_tip.mdx';
 
 > In this example, you'll learn how to set up a simple ClickHouse cluster which
 scales. There are five servers configured. Two are used to shard the data. 
@@ -413,6 +414,8 @@ In this example, each `users.xml` file is identical for all nodes in the cluster
 
 <KeeperConfigExplanation/>
 
+<CloudTip/>
+
 ## Test the setup {#test-the-setup}
 
 Make sure that docker is running on your machine.

docs/deployment-guides/replication-sharding-examples/03_2_shards_2_replicas.md

@@ -15,6 +15,7 @@ import KeeperConfigExplanation from '@site/docs/deployment-guides/replication-sh
 import VerifyKeeperStatus from '@site/docs/deployment-guides/replication-sharding-examples/_snippets/_verify_keeper_using_mntr.mdx';
 import DedicatedKeeperServers from '@site/docs/deployment-guides/replication-sharding-examples/_snippets/_dedicated_keeper_servers.mdx';
 import ExampleFiles from '@site/docs/deployment-guides/replication-sharding-examples/_snippets/_working_example.mdx';
+import CloudTip from '@site/docs/deployment-guides/replication-sharding-examples/_snippets/_cloud_tip.mdx';
 
 > In this example, you'll learn how to set up a simple ClickHouse cluster which
 both replicates and scales. It consisting of two shards and two replicas with a 
@@ -438,6 +439,8 @@ Next you will configure ClickHouse Keeper, which is used for coordination.
 
 <KeeperConfigExplanation/>
 
+<CloudTip/>
+
 ## Test the setup {#test-the-setup}
 
 Make sure that docker is running on your machine.

docs/deployment-guides/replication-sharding-examples/_snippets/_cloud_tip.mdx

@@ -0,0 +1,9 @@
+:::tip Simplified management
+For teams without dedicated database operations expertise, [ClickHouse Cloud](/cloud/overview)
+removes the operational burden associated with managing shards and replicas. The
+platform automatically handles high availability, replication, and scaling decisions.
+Compute and storage are separate and scale based on demand without requiring manual
+configuration or ongoing maintenance.
+
+[Read more](/manage/scaling)
+:::