No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Did you find an answer to this <@U01CL1FL14P>? I've been away from Slack for a few days. We do stuff like this a lot, but the ingress controller is not necessarily created via a chart, so I'd have to look at that part.

Hey <@UMW5G5Z6D> yeah I got it working. At the end it mostly came down to outdated documentation and more specifically - deprecated helm chart used in the MSDN docs. And the new version of the Traefik Helm chart uses hooks, which are not supported by pulumi.

```helm repo add traefik <https://helm.traefik.io/traefik>
helm repo update

# create a controller for ingress with class = 'traefik-public'
helm install traefik-ingress traefik/traefik `
    --namespace $TRAEFIK_INGRESS_CONTROLLER_NAMESPACE `
    --values ./values.yaml `
    --set service.spec.loadBalancerIP=$LOAD_BALANCER_IP `
    --set="additionalArguments={--providers.kubernetesingress.ingressclass=traefik-public}"```

`values.yaml` only contains the following

```rbac:
  enabled: true

providers:
  kubernetesIngress:
    publishedService:
      enabled: true```

Dont ask me what `publishedService.enabled: true` does, the docs are very vague and I remember seeing this somewhere on github in a comment.