No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

image.png

What do you mean with `previously`? did you bump the k8s version between a previous and this deployment?

yes, I had a an earlier K8s version. Since GKE's Rapid release channel constantly updates cluster versions, I even tried the version <https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.17.md#v1178|1.17.8-gke.17>

The issue reproduced itself after the upgrade

are you pods actually healthy? can you check the pod logs/describe them?

<@UCWG26BH7> give me 1 min, I will add cluster credentials to kube_config and check the pods via kubectl or k9s

after that I was planning on enabling logging with max verbosity for pulumi and redirect it to some out file

Traefik pod is fine, it is just pulumi doesn't recognise that it is healthy

can you run `kubectl get endpoints` ? i suspect your service isn't finding those pods correctly. it uses Kubernetes labels to do that

```dmytro.zap@MAC-C02YG37SJGH ~ $ kubectl get endpoints
NAME            ENDPOINTS       AGE
kubernetes      10.2.2.2:443    177m
traefik         &lt;none&gt;          176m
win-webserver   10.206.3.4:80   68m```

Load Balancer should be internal as External one won't have access to my cluster

I think they changed some syntax in their templates, and I just need to figure it out

yeah so the traefik kubernetes service should have labels on it which match the running pods. I'd recommend reading this page to get an idea:
<https://kubernetes.io/docs/concepts/services-networking/service/>

it does look like the helm chart is at fault here, unfortunately

thanks <@UCWG26BH7>, it is definitely not a pulumi issue. I will play with the values file

<@UCWG26BH7>, I added this annotation:
```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"```


It looks like I need to play with labels as you said