better-actor-92669
08/04/2020, 12:51 PMMaster version1.17.7-gke.15
GKE cluster
pulumi==2.7.1
pulumi-gcp==3.16.0
pulumi-kubernetes==2.4.2
pulumi-postgresql==2.3.0
pulumi-random==2.2.0
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?limited-rainbow-51650
08/04/2020, 1:19 PMpreviously
? did you bump the k8s version between a previous and this deployment?better-actor-92669
08/04/2020, 1:38 PMbillowy-army-68599
better-actor-92669
08/04/2020, 1:41 PMbillowy-army-68599
kubectl get endpoints
? i suspect your service isn't finding those pods correctly. it uses Kubernetes labels to do thatbetter-actor-92669
08/04/2020, 1:47 PMdmytro.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-68599
better-actor-92669
08/04/2020, 1:50 PMservice:
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"