Setting up the Yandex Application Load Balancer Ingress controller

To set up a backend group use the HttpBackendGroup CustomResourceDefinition. As a backend, you can use an Application Load Balancer target group or an Object Storage bucket.

To configure Application Load Balancer to work with a backend group:

1. Create a backend group with a bucket:

   1. Create a public bucket in Object Storage.
   2. Configure the website home page and error page.

2. Create a configuration file named demo-app-1.yaml for your application:

   demo-app-1.yaml

   apiVersion: v1
   kind: ConfigMap
   metadata:
     name: alb-demo-1
   data:
     nginx.conf: |
       worker_processes auto;
       events {
       }
       http {
         server {
           listen 80 ;
           location = /_healthz {
             add_header Content-Type text/plain;
             return 200 'ok';
           }
           location / {
             add_header Content-Type text/plain;
             return 200 'Index';
           }
           location = /app1 {
             add_header Content-Type text/plain;
             return 200 'This is APP#1';
           }
         }
       }
   ---
   apiVersion: apps/v1
   kind: Deployment
   metadata:
     name: alb-demo-1
     labels:
       app: alb-demo-1
       version: v1
   spec:
     replicas: 2
     selector:
       matchLabels:
         app: alb-demo-1
     strategy:
       type: RollingUpdate
       rollingUpdate:
         maxSurge: 1
         maxUnavailable: 0
     template:
       metadata:
         labels:
           app: alb-demo-1
           version: v1
       spec:
         terminationGracePeriodSeconds: 5
         volumes:
           - name: alb-demo-1
             configMap:
               name: alb-demo-1
         containers:
           - name: alb-demo-1
             image: nginx:latest
             ports:
               - name: http
                 containerPort: 80
             livenessProbe:
               httpGet:
                 path: /_healthz
                 port: 80
               initialDelaySeconds: 3
               timeoutSeconds: 2
               failureThreshold: 2
             volumeMounts:
               - name: alb-demo-1
                 mountPath: /etc/nginx
                 readOnly: true
             resources:
               limits:
                 cpu: 250m
                 memory: 128Mi
               requests:
                 cpu: 100m
                 memory: 64Mi
   ---
   apiVersion: v1
   kind: Service
   metadata:
     name: alb-demo-1
   spec:
     selector:
       app: alb-demo-1
     type: NodePort
     ports:
       - name: http
         port: 80
         targetPort: 80
         protocol: TCP
         nodePort: 30081
   

3. In a separate directory, create a file named http-group.yaml with the HttpBackendGroup object settings:

   apiVersion: alb.yc.io/v1alpha1
   kind: HttpBackendGroup
   metadata:
     name: example-backend-group
   spec:
     backends: # List of backends.
       - name: alb-demo-1
         weight: 70 # Relative weight of the backend when distributing traffic. The load will be distributed in proportion to the weights of the group's other backends. Specify the weight even if you have only one backend in the group.
         service:
            name: alb-demo-1
            port:
              number: 80
       - name: bucket-backend
         weight: 30
         storageBucket:
           name: <bucket_name>
   

   (Optional) Enter the advanced settings for the controller:

   • spec.backends.useHttp2: To use HTTP/2.
   • spec.backends.tls: Certificate from the certificate authority that the load balancer will trust when establishing a secure connection with backend endpoints. Specify the certificate contents in the trustedCa field as open text.

   For more information, see Backend groups.

4. Create a file named ingress-http.yaml and specify the previously delegated domain name, certificate ID, and settings for Application Load Balancer in it:

   apiVersion: networking.k8s.io/v1
   kind: Ingress
   metadata:
     name: alb-demo-tls
     annotations:
       ingress.alb.yc.io/subnets: <list_of_subnet_IDs>
       ingress.alb.yc.io/security-groups: <list_of_security_group_IDs>
       ingress.alb.yc.io/external-ipv4-address: <IP_address_assignment_method>
       ingress.alb.yc.io/group-name: my-ingress-group
   spec:
     tls:
       - hosts:
         - <domain_name>
         secretName: yc-certmgr-cert-id-<TLS_certificate_ID>
     rules:
       - host: <domain_name>
         http:
           paths:
             - path: /app1
               pathType: Exact
               backend:
                 resource:
                   apiGroup: alb.yc.io
                   kind: HttpBackendGroup
                   name: example-backend-group
   

   Where:

   • ingress.alb.yc.io/subnets: One or more subnets that Application Load Balancer is going to work with.

   • ingress.alb.yc.io/security-groups: One or more security groups for Application Load Balancer. If you skip this parameter, the default security group will be used. At least one of the security groups must allow an outgoing TCP connection to port 10501 in the Managed Service for Kubernetes node group subnet or its security group.

   • ingress.alb.yc.io/external-ipv4-address: Providing public online access to Application Load Balancer. Enter the previously obtained IP address or set auto to obtain a new IP address automatically.

     If you set auto, deleting the Ingress controller will also delete the IP address from the cloud. To avoid this, use an existing reserved IP address.

   • ingress.alb.yc.io/group-name: Group name. Kubernetes Ingress resources are grouped together, each group served by a separate Application Load Balancer instance.

     You can replace my-ingress-group with any group name you like. Make sure it meets the naming requirements.

   (Optional) Enter the advanced settings for the controller:

   • ingress.alb.yc.io/group-settings-name: Name for the Ingress resource group settings to be described in the optional IngressGroupSettings resource. For more information, see Configure the Ingress resource group.

   • ingress.alb.yc.io/internal-ipv4-address: Provide internal access to Application Load Balancer. Enter the internal IP address or use auto to obtain the IP address automatically.

     Note

     You can only use one type of access to Application Load Balancer at a time: ingress.alb.yc.io/external-ipv4-address or ingress.alb.yc.io/internal-ipv4-address.

   • ingress.alb.yc.io/internal-alb-subnet: Subnet for hosting the Application Load Balancer internal IP address. This parameter is required if the ingress.alb.yc.io/internal-ipv4-address parameter is selected.

   • ingress.alb.yc.io/protocol: Connection protocol used by the load balancer and the backends:

     • http: HTTP/1.1, default
     • http2: HTTP/2
     • grpc: gRPC

   • ingress.alb.yc.io/prefix-rewrite: Replace the path for the specified value.

   • ingress.alb.yc.io/upgrade-types: Valid values for the Upgrade HTTP header, e.g., websocket.

   • ingress.alb.yc.io/request-timeout: Maximum period for which the connection can be established.

   • ingress.alb.yc.io/idle-timeout: Maximum connection keep-alive time with zero data transmission.

     Values for request-timeout and idle-timeout must be specified with units of measurement, e.g., 300ms, 1.5h. Acceptable units of measurement include:

     • ns: Nanoseconds
     • us: Microseconds
     • ms: Milliseconds
     • s: Seconds
     • m: Minutes
     • h: Hours

   • ingress.alb.yc.io/security-profile-id: Support for Yandex Smart Web Security that allows you to get protected against DDoS attacks and bots, as well as activate WAF and limit the load to the resource being protected.

     To enable support for Yandex Smart Web Security, specify the previously created Smart Web Security security profile in the Ingress annotation:

     ingress.alb.yc.io/security-profile-id: <security_profile_ID>
     

   • ingress.alb.yc.io/use-regex: Support for RE2 regular expressions when matching the request path. If the true string is provided, the support is enabled. Only applies if the pathType parameter is set to Exact.

   Note

   The settings only apply to the hosts of the given controller rather than the entire Ingress group.

   For more information about the Ingress resource settings, see Ingress resource fields and annotations.

5. Create an Ingress controller, an HttpBackendGroup object, and a Kubernetes app:

   kubectl apply -f .
   

6. Wait until the Ingress controller is created and assigned a public IP address. This may take several minutes.

   To track the progress of controller creation and check that it is error-free, open the logs of the pod where the controller is being created:

   1. In the management console, go to the folder page and select Managed Service for Kubernetes.

   2. Click your cluster's name and select Workload in the left-hand panel.

   3. Select one of the alb-demo-*** pods the Ingress controller is being created on.

   4. Go to the Logs tab on the pod page.

      You will see the Ingress controller creation logged, with the logs displayed in real time. Any errors that occur will also be logged.

7. Make sure the Ingress controller has been created. To do this, run the appropriate command and check that the command output shows the following value in the ADDRESS field:

   kubectl get ingress alb-demo-tls
   

   Result:

   NAME          CLASS   HOSTS           ADDRESS       PORTS    AGE
   alb-demo-tls  <none>  <domain_name>   <IP_address>  80, 443  15h
   

   Based on the Ingress controller configuration, an L7 load balancer will be automatically deployed.