Added Note for adjustment parameters Confluent Cloud service.

docs/integrations/data-ingestion/kafka/confluent/confluent-cloud.md

@@ -60,5 +60,9 @@
 
 The Confluent Cloud UI supports advanced configuration options to adjust poll intervals, batch sizes, and other parameters to optimize performance.
 
+:::note  
+On Confluent Cloud, adjustment of certain settings such as [fetch settings](/integrations/kafka/clickhouse-kafka-connect-sink/#fetch-settings) and [poll settings](/integrations/kafka/clickhouse-kafka-connect-sink/#poll-settings) requires opening a support case through Confluent Cloud.
+:::  
+
 #### Known limitations {#known-limitations}
 * See the list of [Connectors limitations in the official docs](https://docs.confluent.io/cloud/current/connectors/cc-clickhouse-sink-connector/cc-clickhouse-sink.html#limitations)

docs/integrations/data-ingestion/kafka/kafka-clickhouse-connect-sink.md

@@ -448,13 +448,21 @@
 - **`fetch.max.bytes`**: Maximum amount of data to fetch in a single request (default: 52428800 / 50 MB)
 - **`fetch.max.wait.ms`**: Maximum time to wait before returning data if `fetch.min.bytes` is not met (default: 500 ms)
 
+:::note  
+On Confluent Cloud, adjustment of these settings requires opening a support case through Confluent Cloud.  
+:::  
+
 ##### Poll settings {#poll-settings}
 
 The connector polls for messages from the framework's buffer:
 
 - **`max.poll.records`**: Maximum number of records returned in a single poll (default: 500)
 - **`max.partition.fetch.bytes`**: Maximum amount of data per partition (default: 1048576 / 1 MB)
 
+:::note  
+On Confluent Cloud, adjustment of these settings requires opening a support case through Confluent Cloud.  
+:::  
+
 ##### Recommended settings for high throughput {#recommended-batch-settings}
 
 For optimal performance with ClickHouse, aim for larger batches: