I'm getting this error:

Diagnostics:
  pulumi:pulumi:Stack (xxx):
    error: update failed
 
  kubernetes:core:Service (kube-system/prometheus-operator-prometheus):
    error: Plan apply failed: 2 errors occurred:
    
    * Resource operation was cancelled for 'prometheus-operator-prometheus'
    * Service was not allocated an IP address; does your cloud provider support this?

What's really happening ? There are enough IPs in the VPC to provision

@damp-book-35965 you cancelled the operation

Nope..this is repeatedly happening since 2-3 times so now I'm not waiting for it to timeout

when we say the operation was “cancelled” we mean that the kubernetes provider was sent the

Cancel

RPC call.

otherwise stuck on this:

kubernetes:helm.sh:Chart      prometheus-operator                                      
 ~      └─ kubernetes:core:Service    kube-system/prometheus-operator-prometheus  updating..     [2/3] Attempting to allocate IP address to Service

When I wrote this, there was exactly one place where this was called — the ctrl-c handler.

Yes..

what type is your service.

LoadBalancer

@damp-book-35965 when it times out, does it actually have an IP attached?

Nope. it doesnt

sounds like it did not finish initializing then

I think something else is going on..So are you saying we should increase timeout or something :?

no

It's not telling me the reason for not getting an IP .

When I ask whether the service has an IP address attached, I mean when you

kubectl get

it, is there an IP address reported in the

.status

field.

Let me check that

when you say it wasn’t allocated an IP, why did you say no?

Because it's a load balancer type and there is no load balancer spun up on AWS

ok, well, in any event, in general we’ll have no idea why the service does not create a LB.

When I do kubectl get svc it shows external IP as pending

it should. the service controller should be talking to AWS and spinning one up. If it doesn’t work, it’s up to the service controller to report the error through the status field

Yes..

but we don’t know what it is.

Yup..I was wondering what's the logic from the pulumi error message

yeah

Found something else with kubectl describe events

@damp-book-35965 ah, we should be including that information in the error

Yes

Specifically this is part of the work tracked in https://github.com/pulumi/pulumi-kubernetes/issues/133.