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

Hi, I'm running into an error provisioning my stack using `aws-load-balancer-controller 2.5.4` (similar results for 2.5.x):
```    error: resource platform/kafka-mgr was not successfully created by the Kubernetes API server : Internal error occurred: failed calling webhook "mservice.elbv2.k8s.aws": failed to call webhook: the server could not find the requested resource```
Can anyone share a pointer on what could be wrong?

I upgraded `"@pulumi/aws": "^v5.42.0"` and the error message changed to `    error: resource platform/jenkins was not successfully created by the Kubernetes API server : Internal error occurred: failed calling webhook "mservice.elbv2.k8s.aws": failed to call webhook: Post "<https://aws-load-balancer-webhook-service.kube-system.svc:443/mutate-v1-service?timeout=10s>": no endpoints available for service "aws-load-balancer-webhook-service"`

Any pointer to troubleshoot this ^ would be helpful.

I’d say this indicates a problem with the AWS Load Balancer controller running in/on your cluster (this is the piece that creates AWS load balancers in response to the creation of a Service of type LoadBalancer). I’d start by examining that service and see what’s going on with it.

<@UJBNC99MF> Thank you; you were right. I updated `aws-load-balancer-controller` and `amazon/aws-alb-ingress-controller`, which got me past that problem.