service/ingress-nginx-controller annotation

[clickersmudge]

Hi,
I have a Kubernetes cluster in a Hetzner cloud.
Every time I install "ingress-nginx" I have to add the corresponding annotation.

kubectl annotate service --namespace ingress-nginx ingress-nginx-controller load-balancer.hetzner.cloud/location=<LOCATION> # nbg1

Without annotation, LoadBalancer has a pending status all the time.

I set up the whole deployment in Argo CD.

values.yaml

I have added annotation wherever I can
service:
    # -- Enable controller services or not. This does not influence the creation of either the admission webhook or the metrics service.
    enabled: true
    external:
      # -- Enable the external controller service or not. Useful for internal-only deployments.
      enabled: true
    # -- Annotations to be added to the external controller service. See `controller.service.internal.annotations` for annotations to be added to the internal controller service.
    annotations:
      load-balancer.hetzner.cloud/location: nbg1
    # -- Labels to be added to both controller services.
    labels:
      load-balancer.hetzner.cloud/location: nbg1

I added annotation I think everywhere I could, however, it doesn't work.

[longwuyuan]

/remove-kind bug
/triage accepted

post your values.yaml file exactly as it is being used. What you posted is invalid. The field is controller.service.annotation

[longwuyuan]

My values.yaml

% cat values.yaml 
controller:
  service:
    annotations:
      load-balancer.hetzner.cloud/location: nbg1
[~/Documents/ingressnginxissues/11272] 

My controller-service.yaml after helm templating using my values.yaml shows the annotation

% helm install ingress-nginx-2 ingress-nginx/ingress-nginx  \
--namespace ingress-nginx-2 \
--set controller.ingressClassResource.name=nginx-two \
--set controller.ingressClass=nginx-two \
--set controller.ingressClassResource.controllerValue="example.com/ingress-nginx-2" \
--set controller.ingressClassResource.enabled=true \
--set controller.ingressClassByName=true \
--values values.yaml \
--dry-run=client  | grep "controller-service.yaml" -A 6
# Source: ingress-nginx/templates/controller-service.yaml
apiVersion: v1
kind: Service
metadata:
  annotations:
    load-balancer.hetzner.cloud/location: "nbg1"
  labels:
[~/Documents/ingressnginxissues/11272] 

[longwuyuan]

/remove-triage accepted
/kind support

[clickersmudge]

Hi @longwuyuan thank you for your quick response.

Chart.yaml

apiVersion: v2
name: ingress-nginx
description: Ingress controller for Kubernetes using NGINX as a reverse proxy and load balancer

type: application

version: 4.10.0

appVersion: "1.10.0"

dependencies:
- name: ingress-nginx
  version: 4.10.0
  repository: https://kubernetes.github.io/ingress-nginx

values.yaml

controller:
  nodeSelector:
    architecture: arm
  autoscaling:
    enabled: true
  service:
    annotations:
      load-balancer.hetzner.cloud/location: nbg1

Working

I don't know what I was doing wrong earlier.

Maybe other labels
values.yaml

controller:
  nodeSelector:
    architecture: arm
  autoscaling:
    enabled: true
  service:
    annotations:
      load-balancer.hetzner.cloud/location: nbg1
      load-balancer.hetzner.cloud/type: lb11
      load-balancer.hetzner.cloud/use-private-ip: "true"
      load-balancer.hetzner.cloud/disable-private-ingress: "true"

Yes,
it looks like other labels are causing this.

@longwuyuan Do you have any idea what is causing the problem with several labels?

[longwuyuan]

no idea. but almost certainly seems like parsing. do the helm templating and you will know.

Please close the issue if not a problem of the controller.

[longwuyuan]

/close

reopen if there is a problem found in the controller

[k8s-ci-robot]

@longwuyuan: Closing this issue.

In response to this:

/close

reopen if there is a problem found in the controller

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.