adamant-terabyte-3965
06/09/2022, 10:10 PMnew k8s.networking.v1.Ingress
and am failing the pulumi up
with this error:
kubernetes:<http://networking.k8s.io/v1:Ingress|networking.k8s.io/v1:Ingress> (api-ingress):
error: resource test/api-ingress was not successfully created by the Kubernetes API server : admission webhook "vingress.elbv2.k8s.aws" denied the request: invalid ingress class: <http://IngressClass.networking.k8s.io|IngressClass.networking.k8s.io> "alb" not found
The way I have set it up is extremely similar to this blog post: https://www.pulumi.com/blog/kubernetes-ingress-with-aws-alb-ingress-controller-and-pulumi-crosswalk/
Does anyone have any idea what is going wrong?pulumi up
is run a second time it results in a different yet similar set of errors.broad-parrot-2692
06/10/2022, 6:57 PMalb
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