Merge branch 'ClickHouse:main' into code_block_imports

Author: Blargian

docs/about-us/adopters.md

@@ -25,6 +25,13 @@ consume the ClickHouse Cloud API docs, we offer a JSON-based Swagger endpoint
 via https://api.clickhouse.cloud/v1. You can also find the API docs via
 the [Swagger UI](https://clickhouse.com/docs/cloud/manage/api/swagger).
 
+:::note 
+If your organization has been migrated to one of the [new pricing plans](https://clickhouse.com/pricing?plan=scale&provider=aws&region=us-east-1&hours=8&storageCompressed=false), and you use OpenAPI you will be required to remove the `tier` field in the service creation `POST` request.
+
+The `tier` field has been removed from the service object as we no longer have service tiers.  
+This will affect the objects returned by the `POST`, `GET`, and `PATCH` service requests. Therefore, any code that consumes these APIs may need to be adjusted to handle these changes.
+:::
+
 ## Rate limits {#rate-limits}
 
 Developers are limited to 100 API keys per organization. Each API key has a 
@@ -43,6 +50,17 @@ You can view the Terraform provider docs in the [Terraform registry](https://reg
 If you'd like to contribute to the ClickHouse Terraform Provider, you can view 
 the source [in the GitHub repo](https://github.com/ClickHouse/terraform-provider-clickhouse).
 
+:::note 
+If your organization has been migrated to one of the [new pricing plans](https://clickhouse.com/pricing?plan=scale&provider=aws&region=us-east-1&hours=8&storageCompressed=false), you will be required to use our [ClickHouse Terraform provider](https://registry.terraform.io/providers/ClickHouse/clickhouse/latest/docs) version 2.0.0 or above. This upgrade is required to handle changes in the `tier` attribute of the service since, after pricing migration, the `tier` field is no longer accepted and references to it should be removed.
+
+You will now also be able to specify the `num_replicas` field as a property of the service resource.
+:::
+
+## Terraform and OpenAPI New Pricing: Replica Settings Explained
+The number of replicas each service will be created with defaults to 3 for the Scale and Enterprise tiers, while it defaults to 1 for the Basic tier.
+For the Scale and the Enterprise tiers it is possible to adjust it by passing a `numReplicas` field in the service creation request. 
+The value of the `numReplicas` field must be between 2 and 20 for the first service in a warehouse. Services that are created in an existing warehouse can have a number of replicas as low as 1.
+
 ## Support {#support}
 
 We recommend visiting [our Slack channel](https://clickhouse.com/slack) first to get quick support. If 

docs/cloud/manage/api/api-overview.md

@@ -98,7 +98,9 @@ Specifically, services will:
 - Be meant for customers that want additional time to test ClickHouse releases on their non-production environments before the production upgrade. Non-production environments can either get upgrades on the Fast or the Regular release channel for testing and validation.
 
 :::note
-You can change release channels at any time. However, in certain cases, the change will only apply to future releases. For example, if your service is already on the Fast release channel and has received the upgrade, switching to a regular or slow release channel will not downgrade your service to a previous version. It will follow the channel specific release schedule for upcoming updates.
+You can change release channels at any time. However, in certain cases, the change will only apply to future releases. 
+- Moving to a faster channel will immediately upgrade your service. i.e. Slow to Regular, Regular to Fast
+- Moving to a slower channel will not downgrade your service and keep you on your current version until a newer one is available in that channel. i.e. Regular to Slow, Fast to Regular or Slow
 :::
 
 ## Scheduled upgrades {#scheduled-upgrades}

docs/cloud/manage/upgrades.md

@@ -31,6 +31,13 @@ import dashboards from '@site/static/images/cloud/reference/may-30-dashboards.pn
 
 In addition to this ClickHouse Cloud changelog, please see the [Cloud Compatibility](/cloud/reference/cloud-compatibility.md) page.
 
+## August 8, 2025 {#august-08-2025}
+
+- **Notifications**: Users will now receive a UI notification when their service starts upgrading to a new ClickHouse version. Additional Email and Slack notifications can be added via the notification center. 
+- **ClickPipes**: Azure Blob Storage (ABS) ClickPipes support was added to the ClickHouse Terraform provider. See the provider documentation for an example of how to programmatically create an ABS ClickPipe.
+  - [Bug fix] Object storage ClickPipes writing to a destination table using the Null engine now report "Total records" and "Data ingested" metrics in the UI.
+  - [Bug fix] The “Time period” selector for metrics in the UI defaulted to “24 hours” regardless of the selected time period. This has now been fixed, and the UI correctly updates the charts for the selected time period.
+- **Cross-region private link (AWS)** is now Generally Available. Please refer to the [documentation](/manage/security/aws-privatelink) for the list of supported regions.
 
 ## July 31, 2025 {#july-31-2025}
 

docs/cloud/reference/changelog.md

@@ -24,6 +24,11 @@ Classless Inter-domain Routing (CIDR) notation, allows you to specify IP address
 
 ## Create or modify an IP access list {#create-or-modify-an-ip-access-list}
 
+:::note Applicable only to connections outside of PrivateLink
+IP access lists only apply to connections from the public internet, outside of [PrivateLink](/cloud/security/private-link-overview).
+If you only want traffic from PrivateLink, set `DenyAll` in IP Allow list.
+:::
+
 <details>
   <summary>IP access list for ClickHouse services</summary>
 
@@ -63,15 +68,15 @@ This screenshot shows an access list which allows traffic from a range of IP add
 
 <Image img={ip_filter_add_single_ip} size="md" alt="Adding a single IP to the access list in ClickHouse Cloud" border/>
 
-1. Delete an existing entry
+2. Delete an existing entry
 
   Clicking the cross (x) can deletes an entry
 
-1. Edit an existing entry
+3. Edit an existing entry
 
   Directly modifying the entry
 
-1. Switch to allow access from **Anywhere**
+4. Switch to allow access from **Anywhere**
 
   This is not recommended, but it is allowed.  We recommend that you expose an application built on top of ClickHouse to the public and restrict access to the back-end ClickHouse Cloud service.
 

docs/cloud/security/setting-ip-filters.md

@@ -16,7 +16,7 @@ Run the command below from a shell on `clickhouse-keeper-01`, `clickhouse-keeper
 for `clickhouse-keeper-01` is shown below:
 
 ```bash
-docker exec -it clickhouse-keeper-01 echo mntr | nc localhost 9181
+docker exec -it clickhouse-keeper-01  /bin/sh -c 'echo mntr | nc 127.0.0.1 9181'
 ```
 
 The response below shows an example response from a follower node:
@@ -67,4 +67,4 @@ zk_max_file_descriptor_count    18446744073709551615
 zk_followers    2
 zk_synced_followers     2
 # highlight-end
-```
+```

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

@@ -128,7 +128,6 @@ To increase the throughput on large ingest jobs, we recommend scaling the ClickH
 - Role authentication is not available for S3 ClickPipes for ClickHouse Cloud instances deployed into GCP or Azure. It is only supported for AWS ClickHouse Cloud instances.
 - ClickPipes will only attempt to ingest objects at 10GB or smaller in size. If a file is greater than 10GB an error will be appended to the ClickPipes dedicated error table.
 - Azure Blob Storage pipes with continuous ingest on containers with over 100k files will have a latency of around 10–15 seconds in detecting new files. Latency increases with file count.
-- Object Storage ClickPipes ClickPipes inserting into a destination using [Null table engine](/engines/table-engines/special/null) won't have data for "Total records" or "Data ingested" in the UI.
 - Object Storage ClickPipes **does not** share a listing syntax with the [S3 Table Function](/sql-reference/table-functions/s3), nor Azure with the [AzureBlobStorage Table function](/sql-reference/table-functions/azureBlobStorage).
   - `?` — Substitutes any single character
   - `*` — Substitutes any number of any characters except / including empty string

docs/integrations/data-ingestion/clickpipes/object-storage.md

@@ -0,0 +1,92 @@
+---
+title: 'Scaling DB ClickPipes via OpenAPI'
+description: 'Doc for scaling DB ClickPipes via OpenAPI'
+slug: /integrations/clickpipes/postgres/scaling
+sidebar_label: 'Scaling'
+---
+
+:::caution Most users won't need this API
+Default configuration of DB ClickPipes is designed to handle the majority of workloads out of the box. If you think your workload requires scaling, open a [support case](https://clickhouse.com/support/program) and we'll guide you through the optimal settings for the use case.
+:::
+
+Scaling API may be useful for:
+- Large initial loads (over 4 TB)
+- Migrating a moderate amount of data as quickly as possible
+- Supporting over 8 CDC ClickPipes under the same service
+
+Before attempting to scale up, consider:
+- Ensuring the source DB has sufficient available capacity
+- First adjusting [initial load parallelism and partitioning](/integrations/data-ingestion/clickpipes/postgres/parallel_initial_load) when creating a ClickPipe
+- Checking for [long-running transactions](/integrations/clickpipes/postgres/sync_control#transactions-pg-sync) on the source that could be causing CDC delays
+
+**Increasing the scale will proportionally increase your ClickPipes compute costs.** If you're scaling up just for the initial loads, it's important to scale down after the snapshot is finished to avoid unexpected charges. For more details on pricing, see [Postgres CDC Pricing](/cloud/manage/billing/overview#clickpipes-for-postgres-cdc).
+
+## Prerequisites for this process {#prerequisites}
+
+Before you get started you will need:
+
+1. [ClickHouse API key](/cloud/manage/openapi) with Admin permissions on the target ClickHouse Cloud service.
+2. A DB ClickPipe (Postgres, MySQL or MongoDB) provisioned in the service at some point in time. CDC infrastructure gets created along with the first ClickPipe, and the scaling endpoints become available from that point onwards.
+
+## Steps to scale DB ClickPipes {#cdc-scaling-steps}
+
+Set the following environment variables before running any commands:
+
+```bash
+ORG_ID=<Your ClickHouse organization ID>
+SERVICE_ID=<Your ClickHouse service ID>
+KEY_ID=<Your ClickHouse key ID>
+KEY_SECRET=<Your ClickHouse key secret>
+```
+
+Fetch the current scaling configuration (optional):
+
+```bash
+curl --silent --user $KEY_ID:$KEY_SECRET \
+https://api.clickhouse.cloud/v1/organizations/$ORG_ID/services/$SERVICE_ID/clickpipesCdcScaling \
+| jq
+
+# example result:
+{
+  "result": {
+    "replicaCpuMillicores": 2000,
+    "replicaMemoryGb": 8
+  },
+  "requestId": "04310d9e-1126-4c03-9b05-2aa884dbecb7",
+  "status": 200
+}
+```
+
+Set the desired scaling. Supported configurations include 1-24 CPU cores with memory (GB) set to 4× the core count:
+
+```bash
+cat <<EOF | tee cdc_scaling.json
+{
+  "replicaCpuMillicores": 24000,
+  "replicaMemoryGb": 96
+}
+EOF
+
+curl --silent --user $KEY_ID:$KEY_SECRET \
+-X PATCH -H "Content-Type: application/json" \
+https://api.clickhouse.cloud/v1/organizations/$ORG_ID/services/$SERVICE_ID/clickpipesCdcScaling \
+-d @cdc_scaling.json | jq
+```
+
+Wait for the configuration to propagate (typically 3-5 minutes). After the scaling is finished, the GET endpoint will reflect the new values:
+
+```bash
+curl --silent --user $KEY_ID:$KEY_SECRET \
+https://api.clickhouse.cloud/v1/organizations/$ORG_ID/services/$SERVICE_ID/clickpipesCdcScaling \
+| jq
+
+# example result:
+{
+  "result": {
+    "replicaCpuMillicores": 24000,
+    "replicaMemoryGb": 96
+  },
+  "requestId": "5a76d642-d29f-45af-a857-8c4d4b947bf0",
+  "status": 200
+}
+```

docs/integrations/data-ingestion/clickpipes/postgres/scaling.md

@@ -1,5 +1,5 @@
 ---
-slug: /integrations/index
+slug: /integrations/data-sources/index
 keywords: ['AWS S3', 'Azure Data Factory', 'PostgreSQL', 'Kafka', 'MySQL', 'Cassandra', 'Data Factory', 'Redis', 'RabbitMQ', 'MongoDB', 'Google Cloud Storage', 'Hive', 'Hudi', 'Iceberg', 'MinIO', 'Delta Lake', 'RocksDB', 'Splunk', 'SQLite', 'NATS', 'EMQX', 'local files', 'JDBC', 'ODBC']
 description: 'Datasources overview page'
 title: 'Data Sources'

docs/integrations/data-ingestion/data-sources-index.md

@@ -25,7 +25,7 @@ ClickHouse has a huge number of functions that can be used for data analysis —
     ███████████████  259.37 million
     ```
 - **`COUNTD_UNIQ([my_field])`** *(added in v0.2.0)* — Calculates the approximate number of different values of the argument. Equivalent of [uniq()](/sql-reference/aggregate-functions/reference/uniq/). Much faster than `COUNTD()`.
-- **`DATE_BIN('day', 10, [my_datetime_or_date])`** *(added in v0.2.1)* — equivalent of [`toStartOfInterval()`](/sql-reference/functions/date-time-functions#tostartofinterval) in ClickHouse. Rounds down a Date or Date & Time to the given interval, for example:
+- **`DATE_BIN('day', 10, [my_datetime_or_date])`** *(added in v0.2.1)* — equivalent of [`toStartOfInterval()`](/sql-reference/functions/date-time-functions#toStartOfInterval) in ClickHouse. Rounds down a Date or Date & Time to the given interval, for example:
     ```text
      == my_datetime_or_date == | == DATE_BIN('day', 10, [my_datetime_or_date]) ==
         28.07.2004 06:54:50    |              21.07.2004 00:00:00