Migrating services from an external NLB to L7 ALB, with an internal NLB as a target, using the management console

To migrate a service from an external network load balancer to an L7 load balancer:

1. See the service migration recommendations.
2. Create a migration infrastructure.
3. Create a Smart Web Security profile.
4. Create an internal network load balancer for the NGINX Ingress Controller.
5. Create an L7 load balancer. At this step, you will associate the Smart Web Security profile with a virtual host of the L7 load balancer.
6. Test the L7 load balancer.
7. Migrate user traffic from the external network load balancer to the L7 load balancer.

Service migration recommendationsService migration recommendations

1. Optionally, enable L3-L4 DDoS protection (the OSI model). It will enhance the L7 protection provided by Yandex Smart Web Security after migration.

   To enable L3-L4 protection:

   1. Before the migration, reserve a public static IP address with DDoS protection and use this address for the L7 load balancer's listener. If you already have a protected public IP address for the load balancer, you can keep this address during migration. Otherwise, you will have to change the IP address to a protected one.

   2. Configure a trigger threshold for the protection mechanisms, consistent with the amount of legitimate traffic to the protected resource. To set up this threshold, contact support.

   3. Set the MTU value to 1450 for the targets downstream of the load balancer. For more information, see MTU and TCP MSS.

2. Perform migration during the hours when the user load is at its lowest. If you decided to keep your public IP address, your service will be unavailable during the migration while this IP address is moved from the load balancer to the L7 load balancer. This usually takes a few minutes.

3. When using an L7 load balancer, requests to backends come with the source IP address from the range of internal IP addresses of the subnets specified when creating the L7 load balancer. The original IP address of the request source (user) is specified in the X-Forwarded-For header. If you want to log public IP addresses of users on the web server, reconfigure it.

4. Before the migration, define the minimum number of resource units for the autoscaling settings in the L7 load balancer:

   Select the number of resource units based on the analysis of your service load expressed in:

   • Number of requests per second (RPS).
   • Number of concurrent active connections.
   • Number of new connections per second.
   • Traffic processed per second.

Create your infrastructureCreate your infrastructure

1. Create subnets in three availability zones for the L7 load balancer.

2. Create security groups that allow the L7 load balancer to receive inbound traffic and send it to the targets and allow the targets to receive inbound traffic from the load balancer.

3. When using HTTPS, add the TLS certificate of your service to Yandex Certificate Manager.

4. Optionally, reserve an L3-L4 DDoS-protected static public IP address for the L7 load balancer.

Create a Smart Web Security profileCreate a Smart Web Security profile

Create a Smart Web Security profile by selecting From a preset template.

Use these settings when creating the profile:

• In the Action for the default base rule field, select Allow.
• For the Smart Protection rule, enable Only logging (dry run).

These settings enable logging of traffic information, but no actions will be applied to the traffic. This will reduce the risk of disconnecting users due to profile configuration issues. Further on, you will have the option to disable Only logging (dry run) and configure deny rules for your use case in the security profile.

Create an internal network load balancer for the NGINX Ingress ControllerCreate an internal network load balancer for the NGINX Ingress Controller

1. Create an internal network load balancer for the NGINX Ingress controller. Select an option that agrees with the method you initially used to deploy your NGINX Ingress controller:

   Using a Helm chart

   Using a manifest

   1. Add the configuration parameters for the internal network load balancer to the values.yaml file you used to initially configure the NGINX Ingress controller. Leave the other parameters in the file unchanged.

      controller:
        service:
          external:
            enabled: true
          internal:
            enabled: true
            annotations:
              yandex.cloud/load-balancer-type: internal
              yandex.cloud/subnet-id: <subnet_ID_for_internal_network_load_balancer_IP_address>
            loadBalancerIP: <IP_address_of_internal_network_load_balancer_listener>
            externalTrafficPolicy: Local
      

   2. Use this command to apply the NGINX Ingress controller configuration changes:

      helm upgrade <NGINX_Ingress_controller_name> -f values.yaml <chart_for_NGINX_Ingress_controller> -n <namespace>
      

   1. Create a YAML file and describe the Service resource in it:

      apiVersion: v1
      kind: Service
      metadata:
        name: <resource_name>
        namespace: <namespace>
        annotations:
          yandex.cloud/load-balancer-type: internal
          yandex.cloud/subnet-id: <subnet_ID_for_internal_network_load_balancer_IP_address>
      spec:
        type: LoadBalancer
        externalTrafficPolicy: Local
        loadBalancerIP: <IP_address_of_internal_network_load_balancer_listener>
        ports:
        - port: <80_or_another_port_number_for_HTTP>
          targetPort: <80_or_another_port_number_for_NGINX_Ingress_controller_pod_for_HTTP>
          protocol: TCP
          name: http
        - port: <443_or_another_port_number_for_HTTPS>
          targetPort: <443_or_another_port_number_for_NGINX_Ingress_controller_pod_for_HTTPS>
          protocol: TCP
          name: https
        selector:
          <NGINX_Ingress_controller_pod_selectors>
      

   2. Apply the changes using this command:

   kubectl apply -f <Service_resource_file>
   

2. Wait until the internal network load balancer is created and a matching Service object appears. You can use this command to view information about the services:

   kubectl get service
   

Create an L7 load balancerCreate an L7 load balancer

1. Create a target group for the L7 load balancer. Under Targets, select Outside VPC and specify an internal IP address for the internal network load balancer. Click Add target resource and then Create.

2. Create a backend group with the following settings:

   1. Select HTTP as the backend group type.

   2. Under Backends, click Add and set up the backend:

      • Type: Target group.
      • Target groups: Target group you created earlier.
      • Port: TCP port configured for your internal network load balancer's listener. Usually, this is port 80 for HTTP and port 443 for HTTPS.
      • Under Protocol settings, select HTTP or HTTPS depending on the protocol used by your service.
      • Under HTTP health check, delete the health check. Do not add it, as the network load balancer used as the target is a fault-tolerant service.

3. Create an HTTP router.

   Under Virtual hosts, click Add virtual host and configure the virtual host:

   • Authority: Your service domain name.

   • Security profile: Smart Web Security profile you created earlier.

     Warning

     Smart Web Security cannot be made operational without linking a security profile to the L7 load balancer's virtual host.

   • Click Add route and configure the route:

     • Path: Starts with /.
     • Action: Routing.
     • Backend group: Backend group you created earlier.

   You can add multiple domains by clicking Add virtual host.

4. Create an L7 load balancer by selecting Manual:

   1. Specify the security group you created earlier.

      Warning

      The node groups in the Managed Service for Kubernetes cluster must have inbound security group rules allowing traffic from the L7 load balancer on ports 30000-32767, coming either from its subnets or its security group.

   2. Under Allocation, select subnets in three availability zones for the load balancer nodes. Enable traffic in these subnets.

   3. Under Autoscaling settings, specify the minimum number of resource units per availability zone based on expected load.

   4. Under Listeners, click Add listener and set up the listener:

      1. Under Public IP address, specify:

         • Port: TCP port configured for your internal network load balancer's listener. Usually, this is port 80 for HTTP and port 443 for HTTPS.
         • Type: List. Select a public IP address from the list. If you plan to enable DDoS protection at levels L3-L4, select a static public IP address with DDoS protection installed.

      2. Under Receiving and processing traffic, specify:

         • Listener type: HTTP.
         • Protocol: Select HTTP or HTTPS depending on the protocol your service uses.
         • If you select HTTPS, specify the TLS certificate you added to Certificate Manager earlier in the Certificates field.
         • HTTP router: Select the HTTP router you created earlier.

Test the L7 load balancerTest the L7 load balancer

1. Wait until the L7 load balancer goes Active.

2. Navigate to the new L7 load balancer and select Health checks on the left. Make sure you get HEALTHY for all checks.

3. Run a test request to the service through the L7 load balancer, for example, using one of these methods:

   • Add this record to the hosts file on your workstation: <L7_load_balancer_public_IP_address> <service_domain_name>. Delete the record after the test.

   • Execute the request using cURL depending on the protocol type:

     curl http://<service_domain_name> \
         --resolve <service_domain_name>:<service_port>:<public_IP_address_of_L7_load_balancer>
     

     curl https://<service_domain_name> \
         --resolve <service_domain_name>:<service_port>:<public_IP_address_of_L7_load_balancer>
     

Migrate user traffic from the external network load balancer to the L7 load balancerMigrate user traffic from the external network load balancer to the L7 load balancer

Select one of these migration options:

• Keep the public IP address for your service.
• Do not keep the public IP address for your service.

Keep the public IP address for your serviceKeep the public IP address for your service

1. If your external network load balancer is using a dynamic public IP address, convert it to a static one.

2. Delete the external network load balancer. Select an option that agrees with the method you initially used to deploy your NGINX Ingress Controller:

   Using a Helm chart

   Using a manifest

   1. In the values.yaml file you used to initially configure the NGINX Ingress Controller, under controller.service.external, set enabled: false. Leave the other parameters in the file unchanged.

      controller:
        service:
          external:
            enabled: false
          ...
      

   2. Use this command to apply the configuration changes for the NGINX Ingress Controller:

      helm upgrade <NGINX_Ingress_Controller_name> -f values.yaml <chart_for_NGINX_Ingress_Controller> -n <namespace>
      

   Delete the Service resource for the external network load balancer using this command:

   kubectl delete service <name_of_Service_resource_for_external_network_load_balancer>
   

3. Wait until the external network load balancer for the NGINX Ingress Controller and its respective Service object are deleted. You can use this command to view information about the services:

   kubectl get service
   

   This will make your service unavailable through the external network load balancer.

4. In the L7 load balancer, assign to the listener the public IP address previously assigned to the external network load balancer.

   CLI

   If you do not have the Yandex Cloud CLI installed yet, install and initialize it.

   By default, the CLI uses the folder specified when creating the profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also set a different folder for any specific command using the --folder-name or --folder-id parameter.

   To change the public IP address, run this command:

   yc application-load-balancer load-balancer update-listener <load_balancer_name> \
      --listener-name <listener_name> \
      --external-ipv4-endpoint address=<service_public_IP_address>,port=<service_port>
   

   Where address is the public IP address previously assigned to the external network load balancer.

5. After the IP address changes, your service will again be available through the L7 load balancer. Monitor the L7 load balancer's user traffic on the load balancer statistics charts.

6. Delete the now free static public IP address you selected when creating the L7 load balancer.

Do not keep the public IP address for your serviceDo not keep the public IP address for your service

1. To migrate user traffic from an external network load balancer to an L7 load balancer, in the DNS service of your domain's public zone, update the A record value for the service domain name to point to the L7 load balancer's public IP address. If the public domain zone was created in Yandex Cloud DNS, update the record using this guide.

   Note

   The migration may take a while because the propagation of DNS record's updates depends on its time-to-live (TTL) and the number of links in the DNS request chain.

2. As the DNS record updates propagate, monitor the increase in requests to the L7 load balancer on the load balancer statistics charts.

3. Monitor the decrease in traffic on the external network load balancer using the processed_bytes and processed_packets load balancer metrics. You can create a dashboard to visualize these metrics. If there is no load on the network load balancer for a long time, the migration to the L7 load balancer is complete.

4. Optionally, once migration is complete, delete the external network load balancer. Select an option that agrees with the method you initially used to deploy your NGINX Ingress Controller:

   Using a Helm chart

   Using a manifest

   1. In the values.yaml file you used to initially configure the NGINX Ingress Controller, under controller.service.external, set enabled: false. Leave the other parameters in the file unchanged.

      controller:
        service:
          external:
            enabled: false
          ...
      

   2. Use this command to apply the configuration changes for the NGINX Ingress Controller:

      helm upgrade <NGINX_Ingress_Controller_name> -f values.yaml <chart_for_NGINX_Ingress_Controller> -n <namespace>
      

   Warning

   When you update the NGINX Ingress Controller configuration, your service will be temporarily unavailable.

   Delete the Service resource for the external network load balancer using this command:

   kubectl delete service <name_of_Service_resource_for_external_network_load_balancer>
   

5. Optionally, wait until the external network load balancer for the NGINX Ingress Controller and its respective Service object are deleted. You can use this command to view information about the services:

   kubectl get service