Ingress addon (traefik based) create an unnecessary loadbalancer service

[stalb]

Summary

The new ingress addon (based on Traefik), create an unnecessary loadbalancer service when deploying the Traefik helm chart.

The ingress addon uses a deamonset with hostPort mappings, so in this configuration there is no need for a loadbalancer service to route the requests to the traefik pods.

What Should Happen Instead?

The addon should not create the unnecessary loadbalancer service.

Reproduction Steps

1. Deploy the new (Traefik based) ingress addon.
2. Verify that a loadbalancer service is created: kubectl -n ingress get svc

Can you suggest a fix?

In the ingress addon value.yaml file add:

service:
  enabled: false

Are you interested in contributing with a fix?

yes

[giner]

There was a reason to have it before so it needs to be re-evaluated canonical/microk8s#225

[stalb]

@giner If I'm right Traefik Helm chart uses providers.kubernetesGateway.statusAddress.ip, providers.kubernetesIngress.ingressEndpoint.ip and providers.kubernetesIngressNginx.publishStatusAddress for that,
and that doesn't require to have a service.

Remark: since v40.0.0 providers.kubernetesIngressNginx has been renamed providers.kubernetesIngressNGINX.