Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
    • Yandex Cloud Partner program
  • Blog
  • Pricing
  • Documentation
© 2025 Direct Cursus Technology L.L.C.
Yandex Application Load Balancer
  • Getting started
    • Overview
    • Configuring security groups
    • Working with service accounts
    • Creating or updating resources based on a configuration
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • L7 load balancer logs
  • Release notes
  1. Tools for Managed Service for Kubernetes
  2. Working with service accounts

Service account for Application Load Balancer tools for Managed Service for Kubernetes

Written by
Yandex Cloud
Updated at February 24, 2025

The Application Load Balancer tools for Managed Service for Kubernetes, i.e., Ingress controller and Gateway API, deploy the infrastructure on behalf of a service account. This account requires the following permissions:

Ingress controller
Gateway API
Service Type of permission required Minimum role
Application Load Balancer
(roles)
Manage service resources alb.editor
Virtual Private Cloud
(roles)
Manage internal or external connectivity depending on load balancer type vpc.publicAdmin (external)
vpc.privateAdmin (internal)
Certificate Manager
(roles)
Obtain certificates (for HTTPS load balancers) certificate-manager.certificates.downloader
Compute Cloud
(roles)
Get information on virtual machines created as Managed Service for Kubernetes cluster nodes compute.viewer
Service Type of permission required Minimum role
Application Load Balancer
(roles)
Manage service resources alb.editor
Virtual Private Cloud
(roles)
Manage internal or external connectivity depending on load balancer type vpc.publicAdmin (external)
vpc.privateAdmin (internal)
Certificate Manager
(roles)
Manage certificates (for HTTPS load balancers) certificate-manager.certificates.admin
Compute Cloud
(roles)
Get information on virtual machines created as Managed Service for Kubernetes cluster nodes compute.viewer

An authorized key is used to authenticate the service account. You must specify the key in the saKeySecretKey value when installing a Helm chart with an Ingress controller or Gateway API. For example, if you created the key via the yc iam key create CLI command and saved it to sa-key.json, the chart installation command may look like this:

helm install \
  --namespace yc-alb \
  --set-file saKeySecretKey=sa-key.json \
  ...

The key will be stored in the yc-alb-ingress-controller-sa-key or yc-alb-gateway-api-controller-sa-key secret in the namespace specified when installing the chart (yc-alb in the above example).

Was the article helpful?

Previous
Configuring security groups
Next
Creating or updating resources based on a configuration
© 2025 Direct Cursus Technology L.L.C.