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

image.png

It might be worth mentioning that if `pulumi up`  is run a second time it results in a different yet similar set of errors.

It's what's on the tin. the `alb` ingress class doesn't exist in your cluster. log into it and run `kubectl get Ingressclasses` and report back what's in there. Some providers like GKE don't ship an actual ingress class into the target cluster, instead it infers it from the default. Try removing whatever annotation you have in your config that specifies an ingress class, and give the AWS documentation a read to learn more about how ingress classes are configured on your ingress