Marketplace

ALB Ingress Controller

Updated December 19, 2024

Application Load Balancer (ALB) Ingress Controller uses Yandex Application Load Balancer for load balancing and traffic distribution across Kubernetes applications.

In Yandex Managed Service for Kubernetes, ALB Ingress Controller runs Yandex Application Load Balancer and all required supporting resources whenever a Kubernetes user declares an Ingress resource in the cluster.

Warning

Updating ALB Ingress Controller from 0.1.x to 0.2.0 or higher implies certain restrictions. You can find out whether they apply to your infrastructure here. Make sure to check this out; otherwise, there might be a risk of conflicts.

Deployment instructions
  1. Create a service account for the Ingress controller to run properly.

  2. Assign the following roles to it:

    • alb.editor: To create the required resources.
    • vpc.publicAdmin: To manage external connectivity.
    • certificate-manager.certificates.downloader: To work with certificates registered in Yandex Certificate Manager.
    • compute.viewer: To use Managed Service for Kubernetes cluster nodes in load balancer target groups.
    • smart-web-security.editor: (Optional) To connect your Yandex Smart Web Security security profile to a virtual host of the L7 load balancer.
  3. Create a static key and save it to a file named sa-key.json:

    yc iam key create \
      --service-account-name <name of service account for Ingress controller> \
      --output sa-key.json
    
  4. Configure the application:

    • Namespace: Select a namespace other than default or create a new one. If you select the default namespace, ALB Ingress Controller may not work correctly.

    • Application name: Enter a name for the application.

    • Folder ID: Specify a folder ID.

    • Cluster ID: Specify a cluster ID.

    • Service account key: Paste the contents of the sa-key.json file.

    • Enable default health checks: Select this option to install the DaemonSet resource in the node group network for application health checks.

      The resource adds pods with traffic monitoring agents to each node. As a result, node and namespace isolation does not affect monitoring, which means you get accurate traffic monitoring info. DaemonSet adds or removes monitoring agents as the number of cluster nodes goes up or down, respectively.

      You can omit this option if you do not need to run cluster health checks or if you are using your own checks. For more information on setting up health checks manually, see Health checking your applications in a Yandex Managed Service for Kubernetes cluster with the Yandex Application Load Balancer Ingress controller.

  5. Click Install.

  6. Wait for the application to change its status to Deployed.

Billing type
Free
Type
Kubernetes® Application
Category
Network infrastructure
Publisher
Yandex Cloud
Use cases
  • Routing traffic between applications.
  • Managing external and internal access to clusters over HTTP (S).
Technical support

Yandex Cloud technical support responds to requests 24/7. The types of requests available and their response time depend on your pricing plan. You can activate paid support in the management console. Learn more about requesting technical support.

Product composition
Helm chartVersion
Pull-command
Documentation
yandex-cloud/yc-alb-ingress/yc-alb-ingress-controller-chartv0.2.15Open
Docker imageVersion
Pull-command
yandex-cloud/yc-alb-ingress/yc-alb-ingress-controller1734529221845333560366993295157731861919890018092v0.2.15
yandex-cloud/yc-alb-ingress/alpine/socat17345292218453335603669932951577318619198900180921.7.4.2-r0
yandex-cloud/yc-alb-ingress/bitnami/kubectl17345292218453335603669932951577318619198900180921.27.2
Terms
By using this product you agree to the and the terms and conditions of the following software: Yandex Cloud Marketplace Terms of Use
Billing type
Free
Type
Kubernetes® Application
Category
Network infrastructure
Publisher
Yandex Cloud