this blog post is unfortunately 3 years old and k8s has changed significantly since then

in a github gist would be great

That is the code for the ALB controller and the ingress, there is other code for things like VPC set up, cluster set up and configuration, IAM Roles, policies, and deployment, but this is what I think is the relevant code? I'm extremely new to Pulumi though.

So I first tried having the IngressClass created by my

aws-load-balancer-controller

by setting the

values:

option

createIngressClassResource

to

true

, and that seems to create the IngressClass just fine on AWS. However, the Ingress controller creation is still failing in its initialization (although it is created) due to the following error from Pulumi CLI:

* resource luke-test/api-ingress was successfully created, but the Kubernetes API server reported that it failed to fully initialize or become live: 'api-ingress' timed out waiting to be Ready
        * Ingress .status.loadBalancer field was not updated with a hostname/IP address.
        for more information about this error, see <https://pulumi.io/xdv72s>

After looking into the Pulumi Troubleshooting page I tried to run a

pulumi refresh

as it suggests, and that resulted in:

Diagnostics:
  kubernetes:<http://networking.k8s.io/v1:Ingress|networking.k8s.io/v1:Ingress> (api-ingress):
    warning: Refreshed resource is in an unhealthy state:
    * Resource 'api-ingress' was created but failed to initialize
    * Ingress .status.loadBalancer field was not updated with a hostname/IP address.
        for more information about this error, see <https://pulumi.io/xdv72s>

while on my AWS console the Ingress reports:

Failed build model due to couldn't auto-discover subnets: unable to discover at least one subnet

If the

pulumi refresh

isn't going to resolve that error, how should I move forward? I've seen similar problems in this Slack and on Github but I'm not sure which of those solutions would be applicable to my current circumstance.

I should also mention that the

aws-load-balancer-controller

is reporting

{
  "level": "error",
  "ts": 1655156031.6442547,
  "logger": "controller-runtime.manager.controller.ingress",
  "msg": "Reconciler error",
  "name": "api-ingress",
  "namespace": "luke-test",
  "error": "couldn't auto-discover subnets: unable to discover at least one subnet"
}

It looks like to me from logs previous to that error the

aws-load-balancer-controller

is creating correctly, but upon detecting the

ingress

this error starts. Is this a problem with Pulumi's automation or my

aws-load-balancer-controller

config?