Enhance Cloud configuration docs

* Adds screenshots
* Links ip restrictions in cluster access

qdrant-landing/content/documentation/cloud/cluster-access.md

@@ -32,3 +32,7 @@ Next to the cluster endpoint which loadbalances requests across all healthy Qdra
 You can finde the node specific endpoints on the cluster detail page in the Qdrant Cloud Console.
 
 ![Cluster node endpoints](/documentation/cloud/cloud-node-endpoints.png)
+
+## Restricting Cluster Access by IP Range
+
+You can restrict access to your cluster by specifying allowed IP ranges. This ensures that only clients connecting from the specified IP ranges can access the cluster. For more information, see [Client IP Restrictions](/documentation/cloud/configure-cluster/#client-ip-restrictions).

qdrant-landing/content/documentation/cloud/configure-cluster.md

@@ -16,6 +16,8 @@ In adition the cloud platform automatically configures the following settings fo
 * The cluster mode is automatically enabled to allow distributed deployments and horizontal scaling.
 * The maximum amount of payload indexes per collection is set to 100. Larger numbers of payload indexes lead to performance degradation (starting with Qdrant v1.16.0).
 
+![Cluster node endpoints](/documentation/cloud/cloud-advanced-configuration.png)
+
 ## Collection Defaults
 
 You can set default values for the configuration of new collections in your cluster. These defaults will be used when creating a new collection, unless you override them in the collection creation request.
@@ -44,6 +46,8 @@ Enables async scorer which uses io_uring when rescoring. See [Qdrant under the h
 
 If configured, only the chosen IP ranges will be allowed to access the cluster. This is useful for securing your cluster and ensuring that only clients coming from trusted networks can connect to it.
 
+![Cluster node endpoints](/documentation/cloud/cloud-ip-restrictions.png)
+
 ## Restart Mode
 
 The cloud platform will automatically choose the optimal restart mode during version upgrades or maintenance for your cluster. If you have a multi-node cluster and one or more collections with a replication factor of at least 2, the cloud platform will use the rolling restart mode. This means that nodes in the cluster will be restarted one at a time, ensuring that the cluster remains available during the restart process.
@@ -52,6 +56,8 @@ If you have a multi-node cluster, but all collections have a replication factor
 
 It is possible to override your cluster's default restart mode in the advanced configuration section of the Cluster Details page.
 
+![Cluster node endpoints](/documentation/cloud/cloud-restart-mode.png)
+
 ## Shard Rebalancing
 
 When you scale your cluster horizontally, the cloud platform will automatically rebalance shards across all nodes in the cluster, ensuring that data is evenly distributed. This is done to ensure that all nodes are utilized and that the performance of the cluster is optimal.
@@ -64,8 +70,13 @@ Qdrant Cloud offers three strategies for shard rebalancing:
 
 You can deactivate automatic shard rebalancing by deselecting the `rebalancing_strategy` option. This is useful if you want to manually control the shard distribution across nodes.
 
+![Cluster node endpoints](/documentation/cloud/cloud-shard-rebalancing.png)
+
+
 ## Rename a Cluster
 
 You can rename a Qdrant Cluster by clicking the pencil icon next to the cluster name on the Cluster Details page. 
 
 Renaming a cluster does not affect its functionality or configuration. The cluster's unique ID and cluster URLs will remain the same.
+
+![Cluster node endpoints](/documentation/cloud/cloud-rename-cluster.png)