Fields and annotations of the Service resource for the Ingress controller

The Service resource corresponds to the Kubernetes service. For the Ingress controller, Application Load Balancer services are backends between which the incoming traffic is distributed within a Managed Service for Kubernetes cluster. Services representing Application Load Balancer backends may be specified in the Ingress resource either directly or as part of HttpBackendGroup backend groups.

Service is a standard Kubernetes resource. Below, you can find the descriptions of the resource fields and annotations the Application Load Balancer tools for Managed Service for Kubernetes interface with. For a full description of the resource configuration, see the Kubernetes documentation.

ServiceService

apiVersion: v1
kind: Service
metadata: <ObjectMeta>
spec: <ServiceSpec>

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

ObjectMetaObjectMeta

name: <string>
annotations:
  ingress.alb.yc.io/protocol: <string>
  ingress.alb.yc.io/transport-security: <string>

Annotations (metadata.annotations)Annotations (metadata.annotations)

Annotations are collections of key:value pairs used for assigning metadata to objects. Annotation values are always of the string data type. For more on annotations, see the Kubernetes documentation.

In Application Load Balancer, annotations are used in the Service resources for Ingress controller configuration only.

You can provide the following annotations for the ObjectMeta object:

• ingress.alb.yc.io/protocol

  Connection protocol for the load balancer and backends described in Ingress:

  • http: HTTP/1.1; default value
  • http2: HTTP/2
  • grpc: gRPC

• ingress.alb.yc.io/transport-security

  Connection encryption protocol for the load balancer and backends specified in Ingress directly (without HttpBackendGroup).

  The acceptable value is tls: TLS with no certificate challenge.

  If no annotation is specified, the load balancer connects to the backends with no encryption.

  For backends belonging to groups, the annotation value is ignored. To encrypt connections between a load balancer and grouped backends, the spec.backend.tls field of the HttpBackendGroup resource is used (see the resource configuration).

ServiceSpecServiceSpec

type: NodePort
ports:
  - <ServicePort>
  -

ServicePortServicePort

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