[HELM] Support values references in service annotations

[jkroepke]

This is an issue as requested in #10084

I would like to use exists values on service annotations. This this useful where ingress-nginx helm chart is a part of an umbrella helm chart.

Example:

global:
  hostname: grafana.example.com

grafana:
  ingress:
    enabled: true
    annotations:
      cert-manager.io/cluster-issuer: letsencrypt
    ingressClassName: nginx
    hosts:
      - '{{ $.Values.global.hostname }}'

ingress-nginx:
  controller:
    service:
      internal:
        annotations:
          # Example for Azure PLS
          service.beta.kubernetes.io/azure-pls-fqdns: "{{ $.Values.global.hostname }}"
          # Example for Open.Stack
          loadbalancer.openstack.org/hostname: "{{ $.Values.global.hostname }}"
          # Example for Hetzner Cloud
          load-balancer.hetzner.cloud/hostname: "{{ $.Values.global.hostname }}"

The grafana and prometheus helm-chart currently supporting this pattern as well:

• https://github.com/prometheus-community/helm-charts/blob/ccd3bf1de4775797574750cf208806336b97ec59/charts/kube-prometheus-stack/templates/prometheus/ingress.yaml#L33
• https://github.com/grafana/helm-charts/blob/061c43b7e297e496d5e36cb185b44add8ad952ae/charts/grafana/templates/ingress.yaml#L32
• https://github.com/dexidp/helm-charts/blob/96381b137fd4efdce03d3e31e99ab569a8e100a7/charts/dex/templates/ingress.yaml#L34

No

No

[k8s-ci-robot]

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

[jkroepke]

See #10084 for an implementation proposal.

[github-actions]

This is stale, but we won't close it automatically, just bare in mind the maintainers may be busy with other tasks and will reach your issue ASAP. If you have any question or request to prioritize this, please reach #ingress-nginx-dev on Kubernetes Slack.

[jkroepke]

Pr to fix is open

[rikatz]

As PR is closed, we can close it right?
/close

[k8s-ci-robot]

@rikatz: Closing this issue.

In response to this:

As PR is closed, we can close it right?
/close

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.