It's not possible to provide LoadBalancer spec or annotations just to coordinator

[jirislav]

I'd like to specify spec.loadBalancerSourceRanges to the coordinator's service in order to control what the underlying SecurityGroup will look like in the downstream AWS NLB.

Additionally, I'd like to set LoadBalancer annotations just to the coordinator service, but currently, these annotations are propagated to both the worker service & the coordinator service. What I want to achieve for example:

kind: Service
metadata:
  annotations:
    external-dns.alpha.kubernetes.io/hostname: trino.example.com # should only apply to coordinator
    service.beta.kubernetes.io/aws-load-balancer-attributes: load_balancing.cross_zone.enabled=false
    service.beta.kubernetes.io/aws-load-balancer-name: trino
    service.beta.kubernetes.io/aws-load-balancer-nlb-target-type: ip
    service.beta.kubernetes.io/aws-load-balancer-scheme: internal
  name: trino
spec:
  type: LoadBalancer
  externalTrafficPolicy: Local
  loadBalancerSourceRanges:
  - 1.2.3.4/32
  - 10.0.0.0/8

But keep Trino as ClusterIp and avoid propagating the annotations there.

[jirislav]

Should be resolved with #369, someone please take a look.