Compare languages | The l2-load-balancer module: примеры

Публикация сервиса через L2LoadBalancer

Publishing an application via L2LoadBalancer

  • Включите модуль:
  • Enable the module:

yaml apiVersion: deckhouse.io/v1alpha1 kind: ModuleConfig metadata: name: l2-load-balancer spec: enabled: true settings: loadBalancerClass: l2-class #опционально version: 1

yaml apiVersion: deckhouse.io/v1alpha1 kind: ModuleConfig metadata: name: l2-load-balancer spec: enabled: true settings: loadBalancerClass: l2-class #optional version: 1

  • Подготовьте приложение, которое хотите опубликовать:
  • Prepare the application to publish:

shell kubectl create deploy nginx –image=nginx

shell kubectl create deploy nginx –image=nginx

  • Создайте ресурс L2LoadBalancer:
  • Deploy the L2LoadBalancer resource:

yaml apiVersion: network.deckhouse.io/v1alpha1 kind: L2LoadBalancer metadata: name: ingress spec: addressPool:

  • 192.168.2.100-192.168.2.150 nodeSelector: node-role.kubernetes.io/loadbalancer: “” # селектор узлов-балансировщиков

yaml apiVersion: network.deckhouse.io/v1alpha1 kind: L2LoadBalancer metadata: name: ingress spec: addressPool:

  • 192.168.2.100-192.168.2.150 nodeSelector: node-role.kubernetes.io/loadbalancer: “”
  • Создайте ресурс Service со специальными аннотациями:
  • Deploy standard resource Service with special annotations:

yaml apiVersion: v1 kind: Service metadata: name: nginx-deployment annotations: network.deckhouse.io/l2-load-balancer-name: ingress network.deckhouse.io/l2-load-balancer-external-ips-count: “3” spec: type: LoadBalancer loadBalancerClass: l2-class ports:

  • port: 8000 protocol: TCP targetPort: 80 selector: app: nginx

yaml apiVersion: v1 kind: Service metadata: name: nginx-deployment annotations: network.deckhouse.io/l2-load-balancer-name: ingress network.deckhouse.io/l2-load-balancer-external-ips-count: “3” spec: type: LoadBalancer loadBalancerClass: l2-class ports:

  • port: 8000 protocol: TCP targetPort: 80 selector: app: nginx

В результате, созданному сервису с типом LoadBalancer будут присвоены адреса в заданном количестве:

As a result, the created Service with the type LoadBalancer will be assigned the specified number of addresses:

shell $ kubectl get svc NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE nginx-deployment LoadBalancer 10.222.130.11 192.168.2.100,192.168.2.101,192.168.2.102 80:30544/TCP 11s

shell $ kubectl get svc NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE nginx-deployment LoadBalancer 10.222.130.11 192.168.2.100,192.168.2.101,192.168.2.102 80:30544/TCP 11s

Полученные EXTERNAL-IP можно прописывать в качестве A-записей для прикладного домена.

The resulting EXTERNAL-IP are ready to use in application DNS-domain.

shell $ curl -s -o /dev/null -w “%{http_code}” 192.168.2.100:8000 200 $ curl -s -o /dev/null -w “%{http_code}” 192.168.2.101:8000 200 $ curl -s -o /dev/null -w “%{http_code}” 192.168.2.102:8000 200

shell $ curl -s -o /dev/null -w “%{http_code}” 192.168.2.100:8000 200 $ curl -s -o /dev/null -w “%{http_code}” 192.168.2.101:8000 200 $ curl -s -o /dev/null -w “%{http_code}” 192.168.2.102:8000 200