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

I'm trying to use a secret as the kubeconfig for the k8s.Provider, but it keeps failing. Does anyone know what I am doing wrong? :disappointed:

```
const kubernetesProvider = new k8s.Provider("metrics", {
  kubeconfig: config.requireSecret("kubeconfig")
});
```

`error: unable to load Kubernetes client configuration from kubeconfig file: invalid configuration: no configuration has been provide`

but the kubeconfig works when used with kubectl

So you get the same error when doing `fs.readFileSync(...` ?

Let me try to reproduce this... give me a few.

Will take a bit, have to spin up a k8s cluster.

Hmm, I'm not able to reproduce this.

How are you using the `kubernetesProvider` object? Are you passing it to each of your kubernetes resources?

e.g.
```
const ns = new k8s.core.v1.Namespace(name, {}, { provider: kubernetesProvider });
```

```
import * as fs from "fs";
import * as pulumi from "@pulumi/pulumi";
import * as k8s from "@pulumi/kubernetes";
const config = new pulumi.Config();

const kconfig = fs.readFileSync("../kubeconfig").toString();
const kubernetesProvider = new k8s.Provider("metrics", {
  kubeconfig: config.requireSecret("kubeconfig")
});

const appLabels = { app: "nginx" };
const deployment = new k8s.apps.v1.Deployment("nginx", {
  spec: {
    selector: { matchLabels: appLabels },
    replicas: 1,
    template: {
      metadata: { labels: appLabels },
      spec: { containers: [{ name: "nginx", image: "nginx" }] }
    }
  }
});

export const name = deployment.metadata.name;
```

I added it to the other file and not my nginx deploy

`config.requireSecret(...)` should definitely work for this so you shouldn't need to do the `fs.readFileSync` part.

Do you know if its possible to create a secret, thats actually a service account token; and access it?

```
export const serviceAccountSecret = new k8s.core.v1.Secret(
  "community-token-pulumi",
  {
    type: "<http://kubernetes.io/service-account-token|kubernetes.io/service-account-token>",
    metadata: {
      annotations: {
        "<http://kubernetes.io/service-account.name|kubernetes.io/service-account.name>": serviceAccount.metadata.name
      }
    }
  }
);
```