[Yandex Cloud documentation](../../index.md) > [Yandex Application Load Balancer](../index.md) > [Tutorials](index.md) > Blue-green and canary deployment of service versions # Enabling a blue-green and canary deployment of web service versions Configure your web service architecture to switch between versions using the two common deployment models: a [blue-green deployment](https://martinfowler.com/bliki/BlueGreenDeployment.html) and a [canary deployment](https://martinfowler.com/bliki/CanaryRelease.html). Both models use two backends: a blue and a green one. First, you deploy a stable version generally available to users on one backend, e.g., the blue one. Then you use the other backend, the green one, to test the next version. When the testing is complete, the backends will switch roles: * In a blue-green deployment, all user traffic switches from one backend to the other right away. * In a canary deployment, traffic switches gradually, starting with only some of the users. After that, the green backend becomes the primary one, and you can use the blue backend to test your next version. As long as your previous version runs on the blue backend, you can roll the service back to it by switching back the roles. In this tutorial, we will use Yandex Object Storage buckets as backends with an L7 Yandex Application Load Balancer switching traffic between them. To reduce content delivery time, the load balancer receives user requests via the Yandex Cloud CDN content delivery network. In our examples, we are going to use the `cdn.yandexcloud.example` and `cdn-staging.yandexcloud.example` domain names. You can use various [supported tools](#supported-tools) to perform these steps. To build an architecture for a blue-green and canary deployment: 1. [Get your cloud ready](#before-you-begin). 1. [Add a certificate to Certificate Manager](#add-certificate). 1. [Create a cloud network and subnets](#create-network). 1. [Create buckets in Object Storage](#create-buckets). 1. [Upload the files of your service to the buckets](#upload-files). 1. [Create Application Load Balancer backend groups](#create-l7backend). 1. [Create an HTTP router and virtual hosts](#create-route-hosts). 1. [Create an L7 load balancer](#create-balancer). 1. [Create a CDN](#create-cdn-resource). 1. [Configure DNS for the service](#configure-dns). 1. [Test the service and version switching](#check). If you no longer need the resources you created, [delete them](#clear-out). ## Supported tools {#supported-tools} You can complete most of the steps in this tutorial using any standard tool, such as the [management console](https://console.yandex.cloud), [Yandex Cloud](../../cli/index.md) and [AWS](../../storage/tools/aws-cli.md) CLIs, Terraform, and the [Yandex Cloud](../../api-design-guide/index.md) API. Each step lists its respective supported tools. Some steps do not support certain tools: * Currently, you cannot use CLIs and Terraform to: * [Create an Application Load Balancer backend group with buckets as backends](#create-l7backend). * Get the domain name of a CDN load balancer when [configuring DNS for the service](#configure-dns). * Disable and enable caching of a CDN when [running a health check and testing version switching](#check). * Currently, you cannot get the domain name of a CDN load balancer through the API when [configuring DNS for the service](#configure-dns). ## Get your cloud ready {#before-you-begin} Sign up for Yandex Cloud and create a [billing account](../../billing/concepts/billing-account.md): 1. Navigate to the [management console](https://console.yandex.cloud) and log in to Yandex Cloud or create a new account. 1. On the **[Yandex Cloud Billing](https://center.yandex.cloud/billing/accounts)** page, make sure you have a billing account linked and it has the `ACTIVE` or `TRIAL_ACTIVE` [status](../../billing/concepts/billing-account-statuses.md). If you do not have a billing account, [create one](../../billing/quickstart/index.md) and [link](../../billing/operations/pin-cloud.md) a cloud to it. If you have an active billing account, you can create or select a [folder](../../resource-manager/concepts/resources-hierarchy.md#folder) for your infrastructure on the [cloud page](https://console.yandex.cloud/cloud). [Learn more about clouds and folders here](../../resource-manager/concepts/resources-hierarchy.md). We will use a folder named `example-folder` in our example. ### Required paid resources {#paid-resources} The infrastructure support costs include: * Fee for data storage in Object Storage, data operations, and outbound traffic (see [Object Storage pricing](../../storage/pricing.md)). * Fee for using the computing resources of the L7 load balancer (see [Application Load Balancer pricing](../pricing.md)). * Fee for outbound traffic from CDN servers (see [Cloud CDN pricing](../../cdn/pricing.md)). * Fee for public DNS queries and DNS zones if using Yandex Cloud DNS (see [Cloud DNS pricing](../../dns/pricing.md)). ## Add a certificate to Certificate Manager {#add-certificate} Certificates from [Yandex Certificate Manager](../../certificate-manager/index.md) are supported. You can [issue a new Let's Encrypt® certificate](../../certificate-manager/operations/managed/cert-create.md) or [upload one of your own](../../certificate-manager/operations/import/cert-create.md). The certificate must be located in the same [folder](../../resource-manager/concepts/resources-hierarchy.md#folder) as your CDN resource. For a Let's Encrypt® certificate, pass an [ownership check](../../certificate-manager/operations/managed/cert-validate.md) for the domain specified in the certificate. ## Create a cloud network and subnets {#create-network} All resources you create will belong to the same [cloud network](../../vpc/concepts/network.md). {% list tabs group=instructions %} - Management console {#console} 1. In the [management console](https://console.yandex.cloud), select `example-folder`. 1. Navigate to **Virtual Private Cloud**. 1. At the top right, click **Create network**. 1. In the **Name** field, specify `canary-network`. 1. In the **Advanced** field, select **Create subnets**. 1. Click **Create network**. - Yandex Cloud CLI {#cli} If you do not have the Yandex Cloud CLI yet, [install and initialize it](../../cli/quickstart.md#install). The folder used by default is the one specified when [creating](../../cli/operations/profile/profile-create.md) the CLI profile. To change the default folder, use the `yc config set folder-id ` command. You can also specify a different folder for any command using `--folder-name` or `--folder-id`. If you access a resource by its name, the search will be limited to the default folder. If you access a resource by its ID, the search will be global, i.e., through all folders based on access permissions. 1. Create a network named `canary-network`: ```bash yc vpc network create canary-network ``` Result: ``` id: enptrcle5q3d******** folder_id: b1g9hv2loamq******** created_at: "2021-11-03T09:25:03Z" name: canary-network default_security_group_id: enpbsnnop4ak******** ``` For more information about the `yc vpc network create` command, see the [CLI reference](../../cli/cli-ref/vpc/cli-ref/network/create.md). 1. Create subnets in all availability zones: * `ru-central1-a`: ```bash yc vpc subnet create canary-subnet-ru-central1-a \ --zone ru-central1-a \ --network-name canary-network \ --range 10.1.0.0/16 ``` Result: ``` id: e9bnnssj8sc8******** folder_id: b1g9hv2loamq******** created_at: "2021-11-03T09:27:00Z" name: canary-subnet-ru-central1-a network_id: enptrcle5q3d******** zone_id: ru-central1-a v4_cidr_blocks: - 10.1.0.0/16 ``` * `ru-central1-b`: ```bash yc vpc subnet create canary-subnet-ru-central1-b \ --zone ru-central1-b \ --network-name canary-network \ --range 10.2.0.0/16 ``` Result: ``` id: e2lghukd9iqo******** folder_id: b1g9hv2loamq******** created_at: "2021-11-03T09:27:39Z" name: canary-subnet-ru-central1-b network_id: enptrcle5q3d******** zone_id: ru-central1-b v4_cidr_blocks: - 10.2.0.0/16 ``` * `ru-central1-d`: ```bash yc vpc subnet create canary-subnet-ru-central1-d \ --zone ru-central1-d \ --network-name canary-network \ --range 10.3.0.0/16 ``` Result: ``` id: b0c3pte4o2kn******** folder_id: b1g9hv2loamq******** created_at: "2021-11-03T09:28:08Z" name: canary-subnet-ru-central1-d network_id: enptrcle5q3d******** zone_id: ru-central1-d v4_cidr_blocks: - 10.3.0.0/16 ``` For more information about the `yc vpc subnet create` command, see the [CLI reference](../../cli/cli-ref/vpc/cli-ref/subnet/create.md). - Terraform {#tf} If you do not have Terraform yet, [install it and configure the Yandex Cloud provider](../../tutorials/infrastructure-management/terraform-quickstart.md#install-terraform). To manage infrastructure using Terraform under a service account or user accounts (a Yandex account, a federated account, or a local user), [authenticate](../../terraform/authentication.md) using the appropriate method. 1. In the configuration file, describe the settings for `canary-network` and its `canary-subnet-ru-central1-a`, `canary-subnet-ru-central1-b`, and `canary-subnet-ru-central1-d` subnets: ```hcl resource "yandex_vpc_network" "canary-network" { name = "canary-network" } resource "yandex_vpc_subnet" "canary-subnet-a" { name = "canary-subnet-ru-central1-a" zone = "ru-central1-a" network_id = "${yandex_vpc_network.canary-network.id}" v4_cidr_blocks = ["10.1.0.0/16"] } resource "yandex_vpc_subnet" "canary-subnet-b" { name = "canary-subnet-ru-central1-b" zone = "ru-central1-b" network_id = "${yandex_vpc_network.canary-network.id}" v4_cidr_blocks = ["10.2.0.0/16"] } resource "yandex_vpc_subnet" "canary-subnet-d" { name = "canary-subnet-ru-central1-d" zone = "ru-central1-d" network_id = "${yandex_vpc_network.canary-network.id}" v4_cidr_blocks = ["10.3.0.0/16"] } ``` For more information, see the [yandex_vpc_network](../../terraform/resources/vpc_network.md) and [yandex_vpc_subnet](../../terraform/resources/vpc_subnet.md) descriptions in the Terraform provider documentation. 1. Make sure the configuration files are correct. 1. In the terminal, navigate to the directory where you created your configuration file. 1. Run a check using this command: ```bash terraform plan ``` If the configuration is correct, the terminal will display a list of the resources and their settings. Otherwise, Terraform will show any detected errors. 1. Deploy the cloud resources. 1. If the configuration is correct, run this command: ```bash terraform apply ``` 1. Confirm creating the resources. - API {#api} 1. Create `canary-network` using the [NetworkService/Create](../../vpc/api-ref/grpc/Network/create.md) gRPC API call or the [create](../../vpc/api-ref/Network/create.md) REST API method. 1. Create `canary-subnet-ru-central1-a`, `canary-subnet-ru-central1-b`, and `canary-subnet-ru-central1-d` subnets in the three [availability zones](../../overview/concepts/geo-scope.md) using the [SubnetService/Create](../../vpc/api-ref/grpc/Subnet/create.md) gRPC API call or the [create](../../vpc/api-ref/Subnet/create.md) REST API method. {% endlist %} ## Create buckets in Object Storage {#create-buckets} {% list tabs group=instructions %} - Management console {#console} 1. In the [management console](https://console.yandex.cloud), select `example-folder`. 1. Navigate to **Object Storage**. 1. Create a blue bucket for the backend stable version: 1. At the top right, click **Create bucket**. 1. In the ** Name** field, enter a name for the bucket. 1. In the **Read objects** and **Read object list** fields, select `For all`. 1. Click **Create bucket**. 1. Similarly, create a green bucket for the backend test version. - AWS CLI {#cli} 1. Create a blue bucket for the backend stable version: ```bash aws --endpoint-url https://storage.yandexcloud.net \ s3 mb s3:// ``` Result: ``` make_bucket: s3:// ``` 1. Enable public access to read objects and their list: ```bash aws --endpoint-url https://storage.yandexcloud.net \ s3api put-bucket-acl \ --bucket \ --acl public-read ``` 1. Similarly, create a green bucket for the backend test version and enable public access to it. - Terraform {#tf} {% note info %} If you access Object Storage via Terraform under a [service account](../../iam/concepts/users/service-accounts.md), [assign](../../iam/operations/sa/assign-role-for-sa.md) to the service account the relevant [role](../../storage/security/index.md#roles-list), e.g., `storage.admin`, for the folder you are going to create the resources in. {% endnote %} 1. Describe the properties for creating a service account and access key in the configuration file: ```hcl ... // Creating a service account resource "yandex_iam_service_account" "sa" { name = "" } // Assigning a role to a service account resource "yandex_resourcemanager_folder_iam_member" "sa-admin" { folder_id = "" role = "storage.admin" member = "serviceAccount:${yandex_iam_service_account.sa.id}" } // Creating a static access key resource "yandex_iam_service_account_static_access_key" "sa-static-key" { service_account_id = yandex_iam_service_account.sa.id description = "static access key for object storage" } ``` 1. Add the properties of the blue (backend stable version) and green (backend test version) buckets to the configuration file: ```hcl ... resource "yandex_storage_bucket" "canary-bucket-blue" { access_key = yandex_iam_service_account_static_access_key.sa-static-key.access_key secret_key = yandex_iam_service_account_static_access_key.sa-static-key.secret_key bucket = "" acl = "public-read" } resource "yandex_storage_bucket" "canary-bucket-green" { access_key = yandex_iam_service_account_static_access_key.sa-static-key.access_key secret_key = yandex_iam_service_account_static_access_key.sa-static-key.secret_key bucket = "" acl = "public-read" } ``` For more information about the `yandex_storage_bucket` resource, see [this Terraform provider guide](../../terraform/resources/storage_bucket.md). 1. Make sure the configuration files are correct. 1. In the terminal, navigate to the directory where you created your configuration file. 1. Run a check using this command: ```bash terraform plan ``` If the configuration is correct, the terminal will display a list of the resources and their settings. Otherwise, Terraform will show any detected errors. 1. Deploy the cloud resources. 1. If the configuration is correct, run this command: ```bash terraform apply ``` 1. Confirm creating the resources. - API {#api} Use the [create](../../storage/s3/api-ref/bucket/create.md) REST API method. {% endlist %} ## Upload the files of your service to the buckets {#upload-files} 1. Create two files, both named `index.html`. They will represent two service versions: version 1 and version 2. {% cut "Example of the `index.html` file, version 1" %} ```html Version 1

Version 1 is working

``` {% endcut %} {% cut "Example of the `index.html` file, version 2" %} ```html Version 2

Version 2 is working

``` {% endcut %} 1. Upload the files to the buckets: {% list tabs group=instructions %} - Management console {#console} 1. In the [management console](https://console.yandex.cloud), select `example-folder`. 1. Navigate to **Object Storage**. 1. Select the blue bucket. 1. Click **Upload** and select `index.html` version 1 for uploading. 1. Similarly, upload `index.html` version 2 to the green bucket. - AWS CLI {#cli} 1. Upload `index.html` version 1 to the blue bucket: ```bash aws --endpoint-url https://storage.yandexcloud.net \ s3 cp v1/index.html s3:///index.html ``` Result: ``` upload: v1/index.html to s3:///index.html ``` 1. Upload `index.html` version 2 to the green bucket: ```bash aws --endpoint-url https://storage.yandexcloud.net \ s3 cp v2/index.html s3:///index.html ``` Result: ``` upload: v2/index.html to s3:///index.html ``` - Terraform {#tf} 1. Add to the configuration file the properties of the `v1/index.html` and `v2/index.html` files uploaded to the blue and green buckets, respectively: ```hcl ... resource "yandex_storage_object" "canary-bucket-blue-index" { bucket = "" key = "index.html" source = "v1/index.html" } resource "yandex_storage_bucket" "canary-bucket-green-index" { bucket = "" key = "index.html" source = "v2/index.html" } ``` For more information about the `yandex_storage_object` resource, see [this Terraform provider guide](../../terraform/resources/storage_object.md). 1. Make sure the configuration files are correct. 1. In the terminal, navigate to the directory where you created your configuration file. 1. Run a check using this command: ```bash terraform plan ``` If the configuration is correct, the terminal will display a list of the resources and their settings. Otherwise, Terraform will show any detected errors. 1. Deploy the cloud resources. 1. If the configuration is correct, run this command: ```bash terraform apply ``` 1. Confirm creating the resources. - API {#api} Use the [upload](../../storage/s3/api-ref/object/upload.md) REST API method. {% endlist %} ## Create a security group {#create-security-group} [Security groups](../../vpc/concepts/security-groups.md) contain rules that allow the L7 load balancer to receive inbound traffic and send it to backend buckets. To create security groups: {% list tabs group=instructions %} - Management console {#console} 1. In the [management console](https://console.yandex.cloud), select **Virtual Private Cloud**. 1. In the left-hand panel, select ![image](../../_assets/console-icons/shield.svg) **Security groups**. 1. At the top right, click **Create security group**. 1. In the **Name** field, specify `canary-sg`. 1. In the **Network** field, select `canary-network`. 1. Under **Rules**, create the following rules using the instructions below the table: | Traffic
direction | Description | Port range | Protocol | Source /
destination | CIDR blocks | | --- | --- | --- | --- | --- | --- | | `Outgoing` | `any` | `All` | `Any` | `CIDR` | `0.0.0.0/0` | | `Inbound` | `ext-http` | `80` | `TCP` | `CIDR` | `0.0.0.0/0` | | `Inbound` | `ext-https` | `443` | `TCP` | `CIDR` | `0.0.0.0/0` | | `Inbound` | `healthchecks` | `30080` | `TCP` | `Load balancer healthchecks` | — | 1. Navigate to the **Egress** or **Ingress** tab. 1. Click **Add**. 1. In the **Port range** field of the window that opens, specify a single port or a port range for traffic to come to or from. 1. In the **Protocol** field, specify the required protocol or leave `Any`. 1. In the **Destination name** or **Source** field, select the rule purpose: * `CIDR`: Rule will apply to the range of IP addresses. In the **CIDR blocks** field, specify the CIDRs and masks of subnets traffic will move to/from. To add multiple CIDRs, click **Add**. * `Load balancer healthchecks`: Rule allowing a load balancer to health-check VMs. 1. Click **Save**. Repeat these steps to create all rules from the table. 1. Click **Save**. - Yandex Cloud CLI {#cli} Run the following command: ```bash yc vpc security-group create canary-sg \ --network-name canary-network \ --rule direction=egress,port=any,protocol=any,v4-cidrs=[0.0.0.0/0] \ --rule direction=ingress,port=80,protocol=tcp,v4-cidrs=[0.0.0.0/0] \ --rule direction=ingress,port=443,protocol=tcp,v4-cidrs=[0.0.0.0/0] \ --rule direction=ingress,port=30080,protocol=tcp,predefined=loadbalancer_healthchecks ``` Result: ``` id: enpd133ngcnr******** folder_id: b1g9hv2loamq******** created_at: "2021-11-03T10:26:16Z" name: canary-sg network_id: enptrcle5q3d******** status: ACTIVE rules: - id: enpkgrpi2gsi******** direction: EGRESS protocol_name: ANY protocol_number: "-1" cidr_blocks: v4_cidr_blocks: - 0.0.0.0/0 - id: enpgssij0i16******** direction: INGRESS ports: from_port: "80" to_port: "80" protocol_name: TCP protocol_number: "6" cidr_blocks: v4_cidr_blocks: - 0.0.0.0/0 - id: enp0bft67j9l******** direction: INGRESS ports: from_port: "443" to_port: "443" protocol_name: TCP protocol_number: "6" cidr_blocks: v4_cidr_blocks: - 0.0.0.0/0 - id: enpmorcimu65******** direction: INGRESS ports: from_port: "30080" to_port: "30080" protocol_name: TCP protocol_number: "6" predefined_target: loadbalancer_healthchecks ``` For more information about the `yc vpc security-group create` command, see the [CLI reference](../../cli/cli-ref/vpc/cli-ref/security-group/create.md). - Terraform {#tf} 1. Add the `canary-sg` security group properties to the configuration file: ```hcl resource "yandex_vpc_security_group" "canary-sg" { name = "canary-sg" network_id = yandex_vpc_network.canary-network.id egress { protocol = "ANY" port = "ANY" v4_cidr_blocks = ["0.0.0.0/0"] } ingress { protocol = "TCP" port = 80 v4_cidr_blocks = ["0.0.0.0/0"] } ingress { protocol = "TCP" port = 443 v4_cidr_blocks = ["0.0.0.0/0"] } ingress { protocol = "TCP" port = 30080 predefined_target = "loadbalancer_healthchecks" } } ``` For more information about resource properties in Terraform, see [this provider guide](../../terraform/resources/vpc_security_group.md). 1. Make sure the configuration files are correct. 1. In the terminal, navigate to the directory where you created your configuration file. 1. Run a check using this command: ```bash terraform plan ``` If the configuration is correct, the terminal will display a list of the resources and their settings. Otherwise, Terraform will show any detected errors. 1. Deploy the cloud resources. 1. If the configuration is correct, run this command: ```bash terraform apply ``` 1. Confirm creating the resources. - API {#api} Use the [SecurityGroupService/Create](../../vpc/api-ref/grpc/SecurityGroup/create.md) gRPC API call or the [create](../../vpc/api-ref/SecurityGroup/create.md) REST API method. To add a rule for load balancer health checks, use the `loadbalancer_healthchecks` parameter in the [SecurityGroupRuleSpec.target.predefined_target](../../vpc/api-ref/grpc/SecurityGroup/create.md#yandex.cloud.vpc.v1.SecurityGroupRuleSpec) field for the gRPC API or the [predefinedTarget](../../vpc/api-ref/SecurityGroup/create.md#yandex.cloud.vpc.v1.CreateSecurityGroupRequest) field for the REST API. {% endlist %} ## Create Application Load Balancer backend groups {#create-l7backend} {% list tabs group=instructions %} - Management console {#console} 1. Create a backend group named `canary-bg-production` with `canary-backend-blue` and `canary-backend-green`: 1. In the [management console](https://console.yandex.cloud), select `example-folder`. 1. Navigate to **Application Load Balancer**. 1. In the left-hand panel, select ![image](../../_assets/console-icons/cubes-3-overlap.svg) **Backend groups**. 1. At the top right, click **Create backend group**. 1. In the **Name** field, specify `canary-bg-production`. 1. Create a backend named `canary-backend-blue`: 1. Under **Backends**, click **Add**. 1. In the **Name** field, specify `canary-backend-blue`. 1. In the **Weight** field, specify `100`. 1. In the **Type** field, select `Bucket`. 1. Select the blue bucket in the **Bucket** field. 1. Create a backend named `canary-backend-green`: 1. Under **Backends**, click **Add**. 1. In the **Name** field, specify `canary-backend-green`. 1. In the **Weight** field, specify `0`. 1. In the **Type** field, select `Bucket`. 1. In the **Bucket** field, select the green bucket. 1. Click **Create**. 1. Similarly, create a backend group named `canary-bg-staging`. Set the `canary-backend-blue` weight to `0` and the `canary-backend-green` weight to `100`. If you are going to complete the next steps in Terraform, copy the IDs of the `canary-bg-production` and `canary-bg-staging` backend groups from the ![image](../../_assets/console-icons/cubes-3-overlap.svg) **Backend groups** tab. - API {#api} Use the [BackendGroupService/Create](../api-ref/grpc/BackendGroup/create.md) gRPC API call or the [create](../api-ref/BackendGroup/create.md) REST API method. {% endlist %} ## Create an HTTP router and virtual hosts {#create-route-hosts} {% list tabs group=instructions %} - Management console {#console} 1. In the [management console](https://console.yandex.cloud), select `example-folder`. 1. Navigate to **Application Load Balancer**. 1. In the left-hand panel, select ![image](../../_assets/console-icons/route.svg) **HTTP routers**. 1. At the top right, click **Create HTTP router**. 1. In the **Name** field, specify `canary-router`. 1. Create a virtual host named `canary-vh-production`: 1. Under **Virtual hosts**, click **Add virtual host**. 1. In the **Name** field, specify `canary-vh-production`. 1. In the **Authority** field, specify `cdn.yandexcloud.example`. 1. Click **Add route**. 1. In the **Name** field, specify `canary-route-production`. 1. In the **Path** field, select `Starts with` and specify the `/` path. 1. From the **HTTP methods** list, select `GET`. 1. In the **Action** field, keep `Routing`. 1. From the **Backend group** list, select `canary-bg-production`. 1. Create a virtual host named `canary-vh-staging`: * **Name**: `canary-vh-production` * **Authority**: `cdn-staging.yandexcloud.example` * Route **Name**: `canary-route-staging` * **Backend group**: `canary-bg-staging` * The other settings are identical to those for `canary-vh-production`. 1. Click **Create**. - Yandex Cloud CLI {#cli} 1. Create an HTTP router named `canary-router`: ```bash yc alb http-router create canary-router ``` Result: ``` id: ds7qd0vj01dj******** name: canary-router folder_id: b1g9hv2loamq******** created_at: "2021-11-03T10:31:41.027649223Z" ``` For more information about the `yc alb http-router create` command, see the [CLI reference](../../cli/cli-ref/application-load-balancer/cli-ref/http-router/create.md). 1. Create a virtual host named `canary-vh-production`: ```bash yc alb virtual-host create canary-vh-production \ --http-router-name canary-router \ --authority cdn.yandexcloud.example ``` Result: ``` done (1s) name: canary-vh-production authority: - cdn.yandexcloud.example ``` For more information about the `yc alb virtual-host create` command, see the [CLI reference](../../cli/cli-ref/application-load-balancer/cli-ref/virtual-host/create.md). 1. Create a route named `canary-route-production` in the `canary-vh-production` virtual host: ```bash yc alb virtual-host append-http-route canary-route-production \ --http-router-name canary-router \ --virtual-host-name canary-vh-production \ --prefix-path-match "/" \ --backend-group-name canary-bg-production ``` Result: ``` done (1s) name: canary-vh-production authority: - cdn.yandexcloud.example routes: - name: canary-route-production http: match: path: prefix_match: / route: backend_group_id: ds7pbm5fj2v0******** ``` For more information about the `yc alb virtual-host append-http-route` command, see the [CLI reference](../../cli/cli-ref/application-load-balancer/cli-ref/virtual-host/append-http-route.md). 1. Create a virtual host named `canary-vh-staging`: ```bash yc alb virtual-host create canary-vh-staging \ --http-router-name canary-router \ --authority cdn-staging.yandexcloud.example ``` Result: ``` done (1s) name: canary-vh-staging authority: - cdn-staging.yandexcloud.example ``` 1. Create a route named `canary-route-staging` in the `canary-vh-staging` virtual host: ```bash yc alb virtual-host append-http-route canary-route-staging \ --http-router-name canary-router \ --virtual-host-name canary-vh-staging \ --prefix-path-match "/" \ --backend-group-name canary-bg-staging ``` Result: ``` done (1s) name: canary-vh-staging authority: - cdn-staging.yandexcloud.example routes: - name: canary-route-staging http: match: path: prefix_match: / route: backend_group_id: ds765atleota******** ``` - Terraform {#tf} 1. Add the settings for the `canary-router` HTTP router, its virtual hosts, and routes to the configuration file : ```hcl ... resource "yandex_alb_http_router" "canary-router" { name = "canary-router" } resource "yandex_alb_virtual_host" "canary-vh-production" { name = "canary-vh-production" http_router_id = ${yandex_alb_http_router.canary-router.id} authority = "cdn.yandexcloud.example" route { name = "canary-route-production" http_route { http_route_action { backend_group_id = "" } } } } resource "yandex_alb_virtual_host" "canary-vh-staging" { name = "canary-vh-staging" http_router_id = ${yandex_alb_http_router.canary-router.id} authority = "cdn-staging.yandexcloud.example" route { name = "canary-route-staging" http_route { http_route_action { backend_group_id = "" } } } } ``` For more information, see the [yandex_alb_http_router](../../terraform/resources/alb_http_router.md) and [yandex_alb_virtual_host](../../terraform/resources/alb_virtual_host.md) descriptions in the Terraform provider documentation. 1. Make sure the configuration files are correct. 1. In the terminal, navigate to the directory where you created your configuration file. 1. Run a check using this command: ```bash terraform plan ``` If the configuration is correct, the terminal will display a list of the resources and their settings. Otherwise, Terraform will show any detected errors. 1. Deploy the cloud resources. 1. If the configuration is correct, run this command: ```bash terraform apply ``` 1. Confirm creating the resources. - API {#api} 1. Create an HTTP router named `canary-router` using the [HttpRouterService/Create](../api-ref/grpc/HttpRouter/create.md) gRPC API call or the [create](../api-ref/HttpRouter/create.md) REST API method. 1. Create the `canary-vh-production` and `canary-vh-staging` virtual hosts bound to the router and their routes using the [VirtualHostService/Create](../api-ref/grpc/VirtualHost/create.md) gRPC API call or the [create](../api-ref/VirtualHost/create.md) REST API method. {% endlist %} ## Create an L7 load balancer {#create-balancer} {% list tabs group=instructions %} - Management console {#console} 1. In the [management console](https://console.yandex.cloud), select `example-folder`. 1. Navigate to **Application Load Balancer**. 1. At the top right, click **Create L7 load balancer**. 1. In the **Name** field, specify `canary-balancer`. 1. Under **Network settings**: 1. In the **Network** field, select `canary-network`. 1. In the **Security groups** field, select `canary-sg`. Leaving this field blank will allow any inbound and outbound traffic for the load balancer. 1. Under **Allocation**, select the three subnets for the load balancer nodes (`canary-subnet-ru-central1-a`, `canary-subnet-ru-central1-b`, and `canary-subnet-ru-central1-d`) and enable traffic to these subnets. 1. Under **Listeners**, click **Add listener** and set up the listener: 1. In the **Name** field, specify `canary-listener`. 1. Under **Public IP address**: * In the **Port** field, specify `80`. * In the **Type** field, select `Automatically`. 1. In the **HTTP router** field, select `canary-router`. 1. Click **Create**. - Yandex Cloud CLI {#cli} 1. Get the subnet IDs for `canary-network`: ```bash yc vpc network list-subnets canary-network ``` Result: ``` +----------------------+-----------------------------+----------------------+----------------------+----------------+---------------+---------------+ | ID | NAME | FOLDER ID | NETWORK ID | ROUTE TABLE ID | ZONE | RANGE | +----------------------+-----------------------------+----------------------+----------------------+----------------+---------------+---------------+ | e9bnnssj8sc8******** | canary-subnet-ru-central1-d | b1g9hv2loamq******** | enptrcle5q3d******** | | ru-central1-d | [10.1.0.0/16] | | e2lghukd9iqo******** | canary-subnet-ru-central1-b | b1g9hv2loamq******** | enptrcle5q3d******** | | ru-central1-b | [10.2.0.0/16] | | b0c3pte4o2kn******** | canary-subnet-ru-central1-a | b1g9hv2loamq******** | enptrcle5q3d******** | | ru-central1-a | [10.3.0.0/16] | +----------------------+-----------------------------+----------------------+----------------------+----------------+---------------+---------------+ ``` For more information about the `yc vpc network list-subnets` command, see the [CLI reference](../../cli/cli-ref/vpc/cli-ref/network/list-subnets.md). 1. Get the `canary-sg` security group ID: ```bash yc vpc security-group get canary-sg | grep "^id" ``` Result: ``` id: enpd133ngcnr******** ``` For more information about the `yc vpc security-group get` command, see the [CLI reference](../../cli/cli-ref/vpc/cli-ref/security-group/get.md). 1. Create a load balancer named `canary-balancer`: ```bash yc alb load-balancer create canary-balancer \ --network-name canary-network \ --security-group-id \ --location zone=ru-central1-a,subnet-id= \ --location zone=ru-central1-b,subnet-id= \ --location zone=ru-central1-d,subnet-id= ``` Result: ``` done (3m0s) id: ds77q7v39b4u******** name: canary-balancer folder_id: b1g9hv2loamq******** status: ACTIVE region_id: ru-central1 network_id: enptrcle5q3d******** allocation_policy: locations: - zone_id: ru-central1-d subnet_id: b0c3pte4o2kn******** - zone_id: ru-central1-b subnet_id: e2lghukd9iqo******** - zone_id: ru-central1-a subnet_id: e9bnnssj8sc8******** log_group_id: ckg23vr4dlks******** security_group_ids: - enpd133ngcnr******** created_at: "2021-11-03T10:55:49.134935148Z" ``` For more information about the `yc alb load-balancer create` command, see the [CLI reference](../../cli/cli-ref/application-load-balancer/cli-ref/load-balancer/create.md). 1. Add a listener to the load balancer: ```bash yc alb load-balancer add-listener \ --name canary-balancer \ --listener-name canary-listener \ --external-ipv4-endpoint port=80 \ --http-router-name canary-router ``` Result: ``` done (43s) id: ds77q7v39b4u******** name: canary-balancer folder_id: b1g9hv2loamq******** status: ACTIVE region_id: ru-central1 network_id: enptrcle5q3d******** listeners: - name: canary-listener endpoints: - addresses: - external_ipv4_address: address: 84.252.133.149 ports: - "80" http: handler: http_router_id: ds7qd0vj01dj******** allocation_policy: locations: - zone_id: ru-central1-d subnet_id: b0c3pte4o2kn******** - zone_id: ru-central1-b subnet_id: e2lghukd9iqo******** - zone_id: ru-central1-a subnet_id: e9bnnssj8sc8******** log_group_id: ckg23vr4dlks******** security_group_ids: - enpd133ngcnr******** created_at: "2021-11-03T10:55:49.134935148Z" ``` For more information about the `yc alb load-balancer add-listener` command, see the [CLI reference](../../cli/cli-ref/application-load-balancer/cli-ref/load-balancer/add-listener.md). - Terraform {#tf} 1. Add the settings for `canary-balancer` to the configuration file: ```hcl ... resource "yandex_alb_load_balancer" "canary-balancer" { name = "canary-balancer" network_id = ${yandex_vpc_network.canary-network.id} security_group_ids = [ ${yandex_vpc_security_group.canary-sg.id} ] allocation_policy { location { zone_id = "ru-central1-a" subnet_id = ${yandex_vpc_subnet.canary-subnet-ru-central1-a.id} } location { zone_id = "ru-central1-b" subnet_id = ${yandex_vpc_subnet.canary-subnet-ru-central1-b.id} } location { zone_id = "ru-central1-d" subnet_id = ${yandex_vpc_subnet.canary-subnet-ru-central1-d.id} } } listener { name = "canary-listener" endpoint { address { external_ipv4_address { } } ports = [80] } http { handler { http_router_id = ${yandex_alb_http_router.canary-router.id} } } } } ``` For more information about the `yandex_alb_load_balancer` resource, see [this Terraform provider guide](../../terraform/resources/alb_load_balancer.md). 1. Make sure the configuration files are correct. 1. In the terminal, navigate to the directory where you created your configuration file. 1. Run a check using this command: ```bash terraform plan ``` If the configuration is correct, the terminal will display a list of the resources and their settings. Otherwise, Terraform will show any detected errors. 1. Deploy the cloud resources. 1. If the configuration is correct, run this command: ```bash terraform apply ``` 1. Confirm creating the resources. - API {#api} Use the [LoadBalancerService/Create](../api-ref/grpc/LoadBalancer/create.md) gRPC API call or the [create](../api-ref/LoadBalancer/create.md) REST API method. {% endlist %} ## Create a CDN resource {#create-cdn-resource} {% list tabs group=instructions %} - Management console {#console} 1. In the [management console](https://console.yandex.cloud), select `example-folder`. 1. Navigate to **Cloud CDN**. 1. Click **Create resource**. 1. Configure the basic CDN resource settings: * Under **Content**: * Enable **Enable access to content**. * In the **Content query** field, select `From one origin`. * In the **Origin type** field, select `L7 load balancer`. * In the **L7 load balancer** field, select `canary-balancer`. * In the **IP address** field, select the IP address assigned to the load balancer (the only one in the list). * In the **Origin request protocol** field, select `HTTP`. * In the **Domain name** field, specify `cdn.yandexcloud.example`. * Click **Add domain name** and specify `cdn-staging.yandexcloud.example`. {% note alert %} The first domain name, `cdn.yandexcloud.example`, will become the primary one, and you will not be able to edit it after you create a CDN resource. {% endnote %} * Under **Additional settings**: * In the **Redirect clients** field, select `HTTP to HTTPS`. * In the **Certificate type** field, specify `Use from Certificate Manager` and select a [certificate](#add-certificate) for the `cdn.yandexcloud.example` and `cdn-staging.yandexcloud.example` domain names. * In the **Host header** field, select `Match client`. 1. Click **Continue**. 1. Under **Caching** in the **CDN** section, enable **CDN caching**. 1. Click **Continue**. 1. Under **HTTP headers and methods**, and **Advanced**, leave the default settings. Click **Continue**. - Yandex Cloud CLI {#cli} 1. Create an origin group named `canary-origin-group` and indicate the load balancer IP address: ```bash yc cdn origin-group create --name "canary-origin-group" \ --origin source=:80,enabled=true ``` Result: ``` id: "90748" folder_id: b1geoelk7fld******** name: canary-origin-group use_next: true origins: - id: "562449" origin_group_id: "90748" source: 51.250.10.216:80 enabled: true ``` For more information about the `yc cdn origin-group create` command, see the [CLI reference](../../cli/cli-ref/cdn/cli-ref/origin-group/create.md). 1. Copy `origin_group_id` from the previous step and create a CDN resource by running this command: ```bash yc cdn resource create \ --cname cdn.yandexcloud.example \ --origin-group-id \ --secondary-hostnames cdn-staging.yandexcloud.example \ --origin-protocol http \ --cert-manager-ssl-cert-id \ --forward-host-header ``` Result: ``` id: bc843k2yinvq******** folder_id: b1ge1elk72ld******** cname: cdn.yandexcloud.example ... active: true ... ... secondary_hostnames: - cdn-staging.yandexcloud.example ... ``` For more information about the `yc cdn resource create` command, see the [CLI reference](../../cli/cli-ref/cdn/cli-ref/resource/create.md). 1. Enable client redirects for the resource: ```bash yc cdn resource update --redirect-http-to-https ``` - Terraform {#tf} 1. Add the CDN settings to the configuration file: ```hcl ... resource "yandex_cdn_origin_group" "my_group" { name = "canary-origin-group" use_next = true origin { source = ":80" backup = false } } resource "yandex_cdn_resource" "my_resource" { cname = "cdn.yandexcloud.example" active = true origin_protocol = "http" secondary_hostnames = ["cdn-staging.yandexcloud.example"] origin_group_id = yandex_cdn_origin_group.my_group.id ssl_certificate { type = "certificate_manager" certificate_manager_id = "" } options { edge_cache_settings = "345600" browser_cache_settings = "1800" ignore_cookie = true ignore_query_params = false } } ``` For more information, see the [yandex_cdn_origin_group](../../terraform/resources/cdn_origin_group.md) and [yandex_cdn_resource](../../terraform/resources/cdn_resource.md) descriptions in the Terraform provider documentation. 1. Make sure the configuration files are correct. 1. In the terminal, navigate to the directory where you created your configuration file. 1. Run a check using this command: ```bash terraform plan ``` If the configuration is correct, the terminal will display a list of the resources and their settings. Otherwise, Terraform will show any detected errors. 1. Deploy the cloud resources. 1. If the configuration is correct, run this command: ```bash terraform apply ``` 1. Confirm creating the resources by typing `yes` and pressing **Enter**. This will create all the resources you need in the specified folder. You can check the new resources and their settings using the [management console](https://console.yandex.cloud). 1. Enable client redirects for the resource. In the CDN resource settings, add this field at the top of the `options` section: ```hcl ... options { redirect_https_to_http = true ... ``` 1. Run a check using this command: ```bash terraform plan ``` If the configuration description is correct, the terminal will display a list of updated resources and their properties. Terraform will show any errors in the configuration. 1. If there are no errors, run this command: ```bash terraform apply ``` 1. Confirm the resource update by typing `yes` in the terminal and pressing **Enter**. This will enable redirects for the resource. - API {#api} Use the [ResourceService/Create](../../cdn/api-ref/grpc/Resource/create.md) gRPC API call or the [create](../../cdn/api-ref/Resource/create.md) REST API method. {% endlist %} ## Configure DNS for the service {#configure-dns} The `cdn.yandexcloud.example` and `cdn-staging.yandexcloud.example` domain names must be mapped to the CDN resource using DNS records. To configure DNS: 1. Get the domain name of the CDN load balancer: {% list tabs group=instructions %} - Management console {#console} 1. In the [management console](https://console.yandex.cloud), select `example-folder`. 1. Navigate to **Cloud CDN**. 1. From the list of CDN resources, select the one with `cdn.yandexcloud.example` as its primary domain name. 1. From **DNS settings** at the bottom of the page, copy the domain name in `e1b83ae3********.topology.gslb.yccdn.ru` format. {% endlist %} 1. On the website of your DNS hosting provider, navigate to the DNS settings. 1. Create or edit CNAME records for `cdn.yandexcloud.example` and `cdn-staging.yandexcloud.example` so that they point to the domain name you copied: ``` cdn CNAME e1b83ae3********.topology.gslb.yccdn.ru cdn-staging CNAME e1b83ae3********.topology.gslb.yccdn.ru ``` {% note info %} Do not use an [ANAME](../../dns/concepts/resource-record.md#aname) resource record with domain names for content distribution; otherwise, the end user will get a response from a CDN server not linked to the user geolocation. The response will always be the same for all users. {% endnote %} If you use Cloud DNS, follow this guide to configure the record: {% cut "Configuring DNS records for Cloud DNS" %} {% list tabs group=instructions %} - Management console {#console} 1. Open the [management console](https://console.yandex.cloud). 1. Navigate to **Cloud DNS**. 1. If you do not have a public DNS zone, create one: 1. Click **Create zone**. 1. In the **Zone** field, enter the website domain name with a trailing dot: `yandexcloud.example.`. 1. In the **Type** field, select `Public`. 1. In the **Name** field, specify `canary-dns-zone`. 1. Click **Create**. 1. Create a CNAME record for `cdn.yandexcloud.example` in the zone: 1. Select `canary-dns-zone`. 1. Click **Create record**. 1. In the **Name** field, specify `cdn`. 1. In the **Type** field, specify `CNAME`. 1. In the **Data** field, paste the value you copied in `e1b83ae3********.topology.gslb.yccdn.ru` format. 1. Click **Create**. 1. Similarly, create a CNAME record for `cdn-staging.yandexcloud.example` in the same zone. In the **Name** field, specify `cdn-staging`. - Yandex Cloud CLI {#cli} 1. If you do not have a public DNS zone, create one: ```bash yc dns zone create \ --name canary-dns-zone \ --zone yandexcloud.example. \ --public-visibility ``` Result: ``` id: dns4rq4taddd******** folder_id: b1g9hv2loamq******** created_at: "2021-11-03T11:03:28.847Z" name: canary-dns-zone zone: yandexcloud.example. public_visibility: {} ``` For more information about the `yc dns zone create` command, see the [CLI reference](../../cli/cli-ref/dns/cli-ref/zone/create.md). 1. In the zone, create a CNAME record for `cdn.yandexcloud.example` and `cdn-staging.yandexcloud.example` with the value you copied in `e1b83ae3********.topology.gslb.yccdn.ru` format: ```bash yc dns zone add-records \ --name canary-dns-zone \ --record "cdn CNAME e1b83ae3********.topology.gslb.yccdn.ru" \ --record "cdn-staging CNAME e1b83ae3********.topology.gslb.yccdn.ru" ``` For more information about the `yc dns zone add-records` command, see the [CLI reference](../../cli/cli-ref/dns/cli-ref/zone/add-records.md). - Terraform {#tf} 1. Add the `canary-dns-zone` settings and the zone’s CNAME records to the configuration file: ``` ... resource "yandex_dns_zone" "canary-dns-zone" { zone = "yandexcloud.example." name = "canary-dns-zone" public = true } resource "yandex_dns_recordset" "canary-recordset-production" { zone_id = ${yandex_dns_zone.canary-dns-zone.id} name = "cdn" type = "CNAME" data = [""] } resource "yandex_dns_recordset" "canary-recordset-staging" { zone_id = ${yandex_dns_zone.canary-dns-zone.id} name = "cdn-staging" type = "CNAME" data = [" \ --path "/index.html" ``` For more information about the `yc cdn cache purge` command, see the [CLI reference](../../cli/cli-ref/cdn/cli-ref/cache/purge.md). - API {#api} 1. Get the ID of the CDN resource you created using the [ResourceService/List](../../cdn/api-ref/grpc/Resource/list.md) gRPC API call or the [list](../../cdn/api-ref/Resource/list.md) REST API method. 1. Delete `index.html` from the cache using the [CacheService/Purge](../../cdn/api-ref/grpc/Cache/purge.md) gRPC API call or the [purge](../../cdn/api-ref/Cache/purge.md) method. {% endlist %} 1. Open `https://cdn-staging.yandexcloud.example/index.html` in your browser. You should see a page indicating version 2. ### Canary deployment of version 2 {#canary-v2} 1. Disable caching of the CDN resource and delete `index.html` from the cache: {% list tabs group=instructions %} - Management console {#console} 1. In the [management console](https://console.yandex.cloud), select `example-folder`. 1. Navigate to **Cloud CDN**. 1. Select the CDN resource you created (the list of resources will contain its primary domain name: `cdn.yandexcloud.example`). 1. Navigate to the **Caching** tab. 1. Click **Edit**. 1. Disable the **CDN caching** option. 1. Click **Save**. - API {#api} 1. Get the ID of the CDN resource you created using the [ResourceService/List](../../cdn/api-ref/grpc/Resource/list.md) gRPC API call or the [list](../../cdn/api-ref/Resource/list.md) REST API method. 1. Disable caching using the [ResourceService/Update](../../cdn/api-ref/grpc/Resource/update.md) gRPC API call or the [list](../../cdn/api-ref/Resource/update.md) REST API method. {% endlist %} 1. Delete `index.html` from the cache: {% list tabs group=instructions %} - Management console {#console} 1. In the [management console](https://console.yandex.cloud), select `example-folder`. 1. Navigate to **Cloud CDN**. 1. Select the CDN resource you created (the list of resources will contain its primary domain name: `cdn.yandexcloud.example`). 1. Navigate to the **Content** tab. 1. Click **Purge cache**. 1. In the **Purge type** field, select `Selective`. 1. Enter the path to the file you uploaded: `/index.html`. 1. Click **Purge cache**. - Yandex Cloud CLI {#cli} 1. Get the ID of the CDN resource you created: ```bash yc cdn resource list ``` Result: ``` +----------------------+--------------------------+--------------------------------+--------------------------------+--------+-------------------------------------------+ | ID | CNAME | CREATED AT | UPDATED AT | ACTIVE | OPTIONS | +----------------------+--------------------------+--------------------------------+--------------------------------+--------+-------------------------------------------+ | bc837xptmpkh******** | cdn.yandexcloud.example | seconds:1637235693 | seconds:1637235693 | true | edge_cache_settings:{enabled:true | | | | nanos:434085000 | nanos:434115000 | | default_value:345600} | | | | | | | cache_http_headers:{value:"accept-ranges" | | | | | | | value:"cache-control" value:"connection" | | | | | | | value:"content-encoding" | | | | | | | value:"content-length" | | | | | | | value:"content-type" | | | | | | | value:"date" value:"etag" | | | | | | | value:"expires" value:"keep-alive" | | | | | | | value:"last-modified" value:"server" | | | | | | | value:"vary"} stale:{enabled:true | | | | | | | value:"error" value:"updating"} | | | | | | | allowed_http_methods:{value:"GET" | | | | | | | value:"POST" value:"HEAD" | | | | | | | value:"OPTIONS"} | +----------------------+--------------------------+--------------------------------+--------------------------------+--------+-------------------------------------------+ ``` 1. Delete the file from the cache: ```bash yc cdn cache purge \ --resource-id \ --path "/index.html" ``` - API {#api} 1. Get the ID of the CDN resource you created using the [ResourceService/List](../../cdn/api-ref/grpc/Resource/list.md) gRPC API call or the [list](../../cdn/api-ref/Resource/list.md) REST API method. 1. Delete `index.html` from the cache using the [CacheService/Purge](../../cdn/api-ref/grpc/Cache/purge.md) gRPC API call or the [purge](../../cdn/api-ref/Cache/purge.md) method. {% endlist %} 1. Configure the `canary-bg-production` backend group so that `canary-backend-green` running version 2 processes 20% of the traffic coming to `cdn.yandexcloud.example`: {% list tabs group=instructions %} - Management console {#console} 1. In the [management console](https://console.yandex.cloud), select `example-folder`. 1. Navigate to **Application Load Balancer**. 1. In the left-hand panel, select ![image](../../_assets/console-icons/cubes-3-overlap.svg) **Backend groups**. 1. Select `canary-bg-production`. 1. Set the `canary-backend-blue` weight to 80 instead of 100: 1. Under **Backends**, find `canary-backend-blue`, click ![image](../../_assets/console-icons/ellipsis.svg), and select **Edit**. 1. In the **Weight** field, specify `80`. 1. Click **Save**. 1. Similarly, set the `canary-backend-green` weight to 20 instead of 0. 1. Click **Save**. - Yandex Cloud CLI {#cli} 1. Set the `canary-backend-blue` weight to 80 instead of 100: ```bash yc alb backend-group update-http-backend \ --backend-group-name canary-bg-production \ --name canary-backend-blue \ --weight 80 ``` Result: ``` done (1s) id: ds7l9puc18c9******** name: canary-bg-production folder_id: b1g9hv2loamq******** http: backends: - name: canary-backend-blue backend_weight: "80" storage_bucket: bucket: created_at: "2021-11-03T10:28:47.680825561Z" ``` For more information about the `yc alb backend-group update-http-backend` command, see the [CLI reference](../../cli/cli-ref/application-load-balancer/cli-ref/backend-group/update-http-backend.md). 1. Set the `canary-backend-green` weight to 20 instead of 0: ```bash yc alb backend-group update-http-backend \ --backend-group-name canary-bg-production \ --name canary-backend-green \ --weight 20 ``` Result: ``` done (1s) id: ds7l9puc18c9******** name: canary-bg-production folder_id: b1g9hv2loamq******** http: backends: - name: canary-backend-green backend_weight: "20" storage_bucket: bucket: created_at: "2021-11-03T10:28:47.680825561Z" ``` - API {#api} Use the [BackendGroupService/UpdateBackend](../api-ref/grpc/BackendGroup/updateBackend.md) gRPC API call or the [updateBackend](../api-ref/BackendGroup/updateBackend.md) REST API method. {% endlist %} 1. Open `https://cdn.yandexcloud.example/index.html` in your browser several times. In about 20% of cases, you should see a page indicating version 2, and in the other cases, version 1. 1. Same as at steps 1-2, configure and check the following traffic allocations between the backends: 1. In the `canary-bg-production` backend group: 50% of traffic to each of the two backends. 1. In the `canary-bg-production` backend group: All traffic goes to `canary-backend-green`. 1. In the `canary-bg-staging` backend group (the `cdn-staging.yandexcloud.example` domain name): All traffic goes to `canary-backend-blue`. 1. Re-enable caching: {% list tabs group=instructions %} - Management console {#console} 1. In the [management console](https://console.yandex.cloud), select `example-folder`. 1. Navigate to **Cloud CDN**. 1. Select the CDN resource you created (the list of resources will contain its primary domain name: `cdn.yandexcloud.example`). 1. Navigate to the **Caching** tab. 1. Click **Edit**. 1. Enable **CDN caching**. 1. Click **Save**. - API {#api} 1. Get the ID of the CDN resource you created using the [ResourceService/List](../../cdn/api-ref/grpc/Resource/list.md) gRPC API call or the [list](../../cdn/api-ref/Resource/list.md) REST API method. 1. Enable caching using the [ResourceService/Update](../../cdn/api-ref/grpc/Resource/update.md) gRPC API call or the [list](../../cdn/api-ref/Resource/update.md) REST API method. {% endlist %} ### Blue-green deployment for rolling back to version 1 {#blue-green-v1-rollback} 1. Disable caching of the CDN resource and delete `index.html` from the cache: {% list tabs group=instructions %} - Management console {#console} 1. In the [management console](https://console.yandex.cloud), select `example-folder`. 1. Navigate to **Cloud CDN**. 1. Select the CDN resource you created (the list of resources will contain its primary domain name: `cdn.yandexcloud.example`). 1. Navigate to the **Caching** tab. 1. Click **Edit**. 1. Disable the **CDN caching** option. 1. Click **Save**. - API {#api} 1. Get the ID of the CDN resource you created using the [ResourceService/List](../../cdn/api-ref/grpc/Resource/list.md) gRPC API call or the [list](../../cdn/api-ref/Resource/list.md) REST API method. 1. Disable caching using the [ResourceService/Update](../../cdn/api-ref/grpc/Resource/update.md) gRPC API call or the [list](../../cdn/api-ref/Resource/update.md) REST API method. {% endlist %} 1. Delete `index.html` from the cache: {% list tabs group=instructions %} - Management console {#console} 1. In the [management console](https://console.yandex.cloud), select `example-folder`. 1. Navigate to **Cloud CDN**. 1. Select the CDN resource you created (the list of resources will contain its primary domain name: `cdn.yandexcloud.example`). 1. Navigate to the **Content** tab. 1. Click **Purge cache**. 1. In the **Purge type** field, select `Selective`. 1. Enter the path to the file you uploaded: `/index.html`. 1. Click **Purge cache**. - Yandex Cloud CLI {#cli} 1. Get the ID of the CDN resource you created: ```bash yc cdn resource list ``` Result: ``` +----------------------+--------------------------+--------------------------------+--------------------------------+--------+-------------------------------------------+ | ID | CNAME | CREATED AT | UPDATED AT | ACTIVE | OPTIONS | +----------------------+--------------------------+--------------------------------+--------------------------------+--------+-------------------------------------------+ | bc837xptmpkh******** | cdn.yandexcloud.example | seconds:1637235693 | seconds:1637235693 | true | edge_cache_settings:{enabled:true | | | | nanos:434085000 | nanos:434115000 | | default_value:345600} | | | | | | | cache_http_headers:{value:"accept-ranges" | | | | | | | value:"cache-control" value:"connection" | | | | | | | value:"content-encoding" | | | | | | | value:"content-length" | | | | | | | value:"content-type" | | | | | | | value:"date" value:"etag" | | | | | | | value:"expires" value:"keep-alive" | | | | | | | value:"last-modified" value:"server" | | | | | | | value:"vary"} stale:{enabled:true | | | | | | | value:"error" value:"updating"} | | | | | | | allowed_http_methods:{value:"GET" | | | | | | | value:"POST" value:"HEAD" | | | | | | | value:"OPTIONS"} | +----------------------+--------------------------+--------------------------------+--------------------------------+--------+-------------------------------------------+ ``` 1. Delete the file from the cache: ```bash yc cdn cache purge \ --resource-id \ --path "/index.html" ``` - API {#api} 1. Get the ID of the CDN resource you created using the [ResourceService/List](../../cdn/api-ref/grpc/Resource/list.md) gRPC API call or the [list](../../cdn/api-ref/Resource/list.md) REST API method. 1. Delete `index.html` from the cache using the [CacheService/Purge](../../cdn/api-ref/grpc/Cache/purge.md) gRPC API call or the [purge](../../cdn/api-ref/Cache/purge.md) method. {% endlist %} 1. Re-route all traffic from the `cdn.yandexcloud.example` domain name back to `canary-backend-blue` running version 1: {% list tabs group=instructions %} - Management console {#console} 1. In the [management console](https://console.yandex.cloud), select `example-folder`. 1. Navigate to **Application Load Balancer**. 1. In the left-hand panel, select ![image](../../_assets/console-icons/cubes-3-overlap.svg) **Backend groups**. 1. Select `canary-bg-production`. 1. Set the `canary-backend-blue` weight to 100 instead of 0: 1. Under **Backends**, find `canary-backend-blue`, click ![image](../../_assets/console-icons/ellipsis.svg), and select **Edit**. 1. In the **Weight** field, specify `100`. 1. Click **Save**. 1. Similarly, set the `canary-backend-green` weight to 0 instead of 100. 1. Click **Save**. - Yandex Cloud CLI {#cli} 1. Set the `canary-backend-blue` weight to 100 instead of 0: ```bash yc alb backend-group update-http-backend \ --backend-group-name canary-bg-production \ --name canary-backend-blue \ --weight 100 ``` Result: ``` done (1s) id: ds7l9puc18c9******** name: canary-bg-production folder_id: b1g9hv2loamq******** http: backends: - name: canary-backend-blue backend_weight: "100" storage_bucket: bucket: created_at: "2021-11-03T10:28:47.680825561Z" ``` 1. Set the `canary-backend-green` weight to 0 instead of 100: ```bash yc alb backend-group update-http-backend \ --backend-group-name canary-bg-production \ --name canary-backend-green \ --weight 0 ``` Result: ``` done (1s) id: ds7l9puc18c9******** name: canary-bg-production folder_id: b1g9hv2loamq******** http: backends: - name: canary-backend-green backend_weight: "0" storage_bucket: bucket: created_at: "2021-11-03T10:28:47.680825561Z" ``` - API {#api} Use the [BackendGroupService/UpdateBackend](../api-ref/grpc/BackendGroup/updateBackend.md) gRPC API call or the [updateBackend](../api-ref/BackendGroup/updateBackend.md) REST API method. {% endlist %} 1. Open `https://cdn.yandexcloud.example/index.html` in your browser several times. Each time, you should see a page indicating version 1. 1. Same as at steps 1-2, switch all traffic from `cdn-staging.yandexcloud.example` to `canary-backend-green` running version 2 and check the switchover in your browser. 1. Re-enable caching: {% list tabs group=instructions %} - Management console {#console} 1. In the [management console](https://console.yandex.cloud), select `example-folder`. 1. Navigate to **Cloud CDN**. 1. Select the CDN resource you created (the list of resources will contain its primary domain name: `cdn.yandexcloud.example`). 1. Navigate to the **Caching** tab. 1. Click **Edit**. 1. Enable **CDN caching**. 1. Click **Save**. - API {#api} 1. Get the ID of the CDN resource you created using the [ResourceService/List](../../cdn/api-ref/grpc/Resource/list.md) gRPC API call or the [list](../../cdn/api-ref/Resource/list.md) REST API method. 1. Enable caching using the [ResourceService/Update](../../cdn/api-ref/grpc/Resource/update.md) gRPC API call or the [list](../../cdn/api-ref/Resource/update.md) REST API method. {% endlist %} ## How to delete the resources you created {#clear-out} To shut down the infrastructure and stop paying for the resources you created: 1. If you set up CNAME records in Cloud DNS, [delete](../../dns/operations/zone-delete.md) the `canary-dns-zone` DNS zone. 1. [Delete](../../cdn/operations/resources/delete-resource.md) the CDN resource with `cdn.yandexcloud.example` as the primary domain name. 1. [Delete](../operations/application-load-balancer-delete.md) `canary-balancer`. 1. [Delete](../../storage/operations/objects/delete.md) all objects from the blue and green buckets. 1. [Delete](../../storage/operations/buckets/delete.md) the blue and green buckets. 1. [Delete](../../vpc/operations/subnet-delete.md) `canary-subnet-ru-central1-a`, `canary-subnet-ru-central1-b`, and `canary-subnet-ru-central1-d`. 1. [Delete](../../vpc/operations/network-delete.md) `canary-network`.