Yandex Cloud
Search
Contact UsTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2026 Direct Cursus Technology L.L.C.
Yandex Application Load Balancer
  • Getting started
    • Overview
      • Overview
      • Installing the Gateway API
        • Gateway
        • GatewayPolicy
        • HTTPRoute
        • GRPCRoute
        • RoutePolicy
        • TLSRoute
        • Gateway API service
        • YCCertificate
        • YCStorageBucket
    • Configuring security groups
    • Working with service accounts
    • Creating and updating resources via ingress controller configurations
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • L7 load balancer logs
  • Release notes

In this article:

  • Service
  • ServiceSpec
  • ServicePort
  1. Tools for Managed Service for Kubernetes
  2. Gateway API
  3. Resource configuration
  4. Gateway API service

Fields and annotations of the Service resource for the Gateway API

Written by
Yandex Cloud
Updated at January 26, 2026
  • Service
  • ServiceSpec
  • ServicePort

The Service resource represents a Kubernetes service. For the Gateway API, services are backends across which incoming traffic is distributed within a Managed Service for Kubernetes cluster. Services operating as Application Load Balancer backends are specified in the HTTPRoute resource.

Service is a standard Kubernetes resource. Below, we describe its fields and annotations used by the Application Load Balancer tools for Managed Service for Kubernetes. For resource configuration details, see this Kubernetes guide.

ServiceService

apiVersion: v1
kind: Service
metadata:
  name: <string>
spec: <ServiceSpec>

Field

Value / Type

Description

apiVersion

v1

This is a required field.

Kubernetes API version.

kind

Service

Resource type.

metadata

ObjectMeta

This is a required field.

Resource metadata.

metadata.name

string

This is a required field.

Resource name.

Do not mistake this name for the Application Load Balancer load balancer name.

spec

ServiceSpec

This is a required field.

Resource specification.

Example
apiVersion: v1
kind: Service
metadata:
  name: alb-demo-1
spec:
  selector:
    app: alb-demo-1
  type: NodePort
  ports:
    - name: http
      port: 80
      protocol: TCP
      nodePort: 30081

ServiceSpecServiceSpec

type: NodePort
ports:
  - <ServicePort>
  -

Field

Value / Type

Description

type

NodePort

This is a required field.

Service type.

Warning

Kubernetes backend services referenced in Ingress rules (directly or via HttpBackendGroup/GrpcBackendGroup), must be of type NodePort. For more information about this type, see the relevant Kubernetes article.

ports

[]ServicePort

This is a required field.

List of ports the service is available on.

ServicePortServicePort

port: <int32>
name: <string>
protocol: <protocol>
nodePort: <int32>

Field

Value / Type

Description

port

int32

This is a required field.
Number of the port the service is available on.

You can use this number if you designate a service as a backend:

  • In Ingress, in the spec.rules.http.paths.backend.service.port.number field (see the configuration).
  • In HttpBackendGroup, in the spec.backends.service.port.number field (see the configuration).

name

string

Service port name.

You can use this name if you designate a service as a backend:

  • In Ingress, in the spec.rules.http.paths.backend.service.port.name field (see the configuration).
  • In HttpBackendGroup, in the spec.backends.service.port.name field (see the configuration).

protocol

TCP

Port network protocol; TCP only.

nodePort

int32

Number of the port opened on the cluster nodes where the service is deployed. The load balancer routes traffic to this port, and Kubernetes forwards the traffic to the service on its port in the port parameter.

The value matches the backend port in the Application Load Balancer backend group.

Was the article helpful?

Previous
TLSRoute
Next
YCCertificate
© 2026 Direct Cursus Technology L.L.C.