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

Hello! Did someone already had issues updating Kubernetes certificates and refreshing pulumi stack? I’m currently getting the following error

```kubernetes:core/v1:PersistentVolume storage-3 refreshing warning: configured Kubernetes cluster is unreachable: unable to load schema information from the API server: the server has asked for the client to provide credentials```

this is coming from your Kubernetes cluster, does `kubectl cluster-info` work?

the error you're showing is a response from the Kubernetes API server

Hi <@UCWG26BH7>:
```Kubernetes master is running at <https://172.16.24.240:6443|https://172.16.24.240:6443>
KubeDNS is running at <https://172.16.24.240:6443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy|https://172.16.24.240:6443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy>```

Seems like the cluster is running successfully, but the credentials used by pulumi Kubernetes provider is still not up to date.