service.beta.kubernetes.io/aws-load-balancer-name doesn't set the load balancer name on new deployment.

[jamrobi2]

Apologies if this is a basic question, but i'm currently stumped, I do have a work around by using tags and they work, but for my own piece of mind...

The following config is used for deploying an nlb.

server:
  replicas: 2
  autoscaling:
    enabled: true
    minReplicas: 2
    maxReplicas: 5

  ingress:
    enabled: false

  service:
    type: LoadBalancer

    annotations:
      # Make the Load Balancer internal
      service.beta.kubernetes.io/aws-load-balancer-internal: "true"
      service.beta.kubernetes.io/aws-load-balancer-name: "argocd-nlb"
      service.beta.kubernetes.io/aws-load-balancer-additional-resource-tags: "Name=argocd-nlb,Environment=dev"
      service.beta.kubernetes.io/aws-load-balancer-type: nlb
      service.beta.kubernetes.io/aws-load-balancer-subnets: "${subnets_string}"
    loadBalancerSourceRanges:
      - 10.0.0.0/8

Everything is working except the name is ALWAYS a generated string, not the name passed in by the service.beta.kubernetes.io/aws-load-balancer-name annotation.

Is this supported, if so how should I be using it?

[yu-croco]

@jamrobi2

except the name is ALWAYS a generated string,

Are you talking about ALB's name ? I wonder your annotations are different from the official doc.

[jamrobi2]

i'm talking nlb see the official doc

[yu-croco]

Everything is working except the name is ALWAYS a generated string, not the name passed in by the service.beta.kubernetes.io/aws-load-balancer-name annotation.

I think this is because of ALBC's specification since argo-helm just sets the annotations.
What about this possibility?

https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.2/guide/service/annotations/#traffic-routing

[yu-croco]

Maybe you can bring the rendered yaml to albc's repo to get more help.

[jamrobi2]

here is the rendered argocd server, trying both beta and not beta versions, no luck, also tried a new deployment due to limitiations mentioned and also my defined name not used.

apiVersion: v1
kind: Service
metadata:
  name: argo-cd-argocd-server
  namespace: default
  labels:
    helm.sh/chart: argo-cd-8.0.14
    app.kubernetes.io/name: argocd-server
    app.kubernetes.io/instance: argo-cd
    app.kubernetes.io/component: server
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/part-of: argocd
    app.kubernetes.io/version: "v1.0.1"
  annotations:
    service.beta.kubernetes.io/aws-load-balancer-internal: "true"
    service.beta.kubernetes.io/aws-load-balancer-name: "test"
    service.beta.kubernetes.io/aws-load-balancer-type: "nlb"
    service.kubernetes.io/aws-load-balancer-name: "test2"
spec:
  type: LoadBalancer  
  externalTrafficPolicy: Cluster
  loadBalancerSourceRanges:
    - 10.0.0.0/8
  sessionAffinity: None
  ports:
  - name: http
    protocol: TCP
    port: 80
    targetPort: 8080
  - name: https
    protocol: TCP
    port: 443
    targetPort: 8080
  selector:
    app.kubernetes.io/name: argocd-server
    app.kubernetes.io/instance: argo-cd
      

[mkilchhofer]

The problem is that the annotation service.beta.kubernetes.io/aws-load-balancer-type: "external" is missing. Only when you use this, you tell that the aws-load-balancer-controller is responsible to reconcile that load balancer.

When this annotation is missing, another controller is reponsible:

Configuration

By default, Kubernetes Service resources of type LoadBalancer get reconciled by the Kubernetes controller built into the CloudProvider component of the kube-controller-manager or the cloud-controller-manager(also known as the in-tree controller).

In order for the LBC to manage the reconciliation of Kubernetes Service resources of type LoadBalancer, you need to offload the reconciliation from the in-tree controller to the LBC, explicitly.

Source: https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.16/guide/service/nlb/#configuration