This message was deleted.

sparse-intern-71089

01/06/2023, 12:25 PM

This message was deleted.

dry-keyboard-94795

01/06/2023, 12:33 PM

KUBECONFIG

should be set to the path of the config, ie

KUBECONFIG=~/.kube/config

If your

.kube/config

is setup already, then pulumi will use that https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#setup

flat-engineer-30260

01/06/2023, 12:38 PM

I knew what you mean. If we're running pulumi up in local environment, that's work. However, we deploy the codes by CI/CD pipeline (pulumi deployment feature), the initial contianer doesn't have ~/.kube/config there, you've pass it into container in some way. That's what block me a long time.

flat-engineer-30260

01/06/2023, 12:41 PM

KUBECONFIG

support path and also content as the docs stated:

dry-keyboard-94795

01/06/2023, 12:47 PM

hmm, from the

--help

, looks like you can set a value through stdin. so this might work for you?

Copy code

cat my/kubeconfig | config set --secret kubernetes:kubeconfig

👍 1

✅ 1

💯 1

flat-engineer-30260

01/06/2023, 12:54 PM

Brilliant! It works. Thank you for saving my time.

flat-engineer-30260

01/06/2023, 1:01 PM

Configuration values can be accessed when a stack is being deployed and used to configure behavior.

If a value is not present on the command line, pulumi will prompt for the value. Multi-line values

may be set by piping a file to standard in.

My bad, I'm not go through the instruction carefully. 😂

6 Views

Open in Slack

Previous Next

Pulumi Community

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.