better-actor-9266908/04/2020, 12:51 PM
Previously, I was able to deploy everything without any issues, so I assume it is either Kubernetes API changes or pulumi's interaction with Kubernetes API. Can someone please help me identify the issue?
pulumi==2.7.1 pulumi-gcp==3.16.0 pulumi-kubernetes==2.4.2 pulumi-postgresql==2.3.0 pulumi-random==2.2.0
limited-rainbow-5165008/04/2020, 1:19 PM
? did you bump the k8s version between a previous and this deployment?
better-actor-9266908/04/2020, 1:38 PM
billowy-army-6859908/04/2020, 1:39 PM
better-actor-9266908/04/2020, 1:41 PM
billowy-army-6859908/04/2020, 1:47 PM
? i suspect your service isn't finding those pods correctly. it uses Kubernetes labels to do that
kubectl get endpoints
better-actor-9266908/04/2020, 1:47 PM
dmytro.zap@MAC-C02YG37SJGH ~ $ kubectl get endpoints NAME ENDPOINTS AGE kubernetes 10.2.2.2:443 177m traefik <none> 176m win-webserver 10.206.3.4:80 68m
billowy-army-6859908/04/2020, 1:49 PM
better-actor-9266908/04/2020, 1:50 PM
service: enabled: true type: LoadBalancer # Additional annotations (e.g. for cloud provider specific config) annotations: # Additional entries here will be added to the service spec. Cannot contains # type, selector or ports entries. cloud.google.com/load-balancer-type: "Internal"