Channels
pulumi-ai
package-authoring
pulumi-cdk
oracle-cloud-infrastructure
learn-pulumi-events
linen
registry
built-with-pulumi
pulumi-cloud
contribex
testingtesting321
hacktoberfest
cloudengineering
yaml
pulumi-crosscode
content-share
finops
multi-language-hackathon
office-hours
workshops
blog-posts
localstack
welcome
gitlab
pulumi-kubernetes-operator
jobs
aws
pulumi-deployments
dotnet
golang
announcements
java
pulumiverse
python
install
getting-started
cloudengineering-support
testingtesting123
hackathon-03-19-2020
typescript
google-cloud
contribute
azure
kubernetes
docs
automation-api
status
general
Title
b
busy-umbrella-36067
01/07/2020, 11:31 PMAnyone else getting this issue? Not sure if its related to the latest provider release
We don’t use implicit provider
kubeconfigeks.Cluster.providerError: invocation of kubernetes:yaml:decode returned an error: unable to load Kubernetes client configuration from kubeconfig file: invalid configuration: no configuration has been provided
at monitor.invoke (/root/project/node_modules/@pulumi/pulumi/runtime/invoke.js:172:33)
at Object.onReceiveStatus (/root/project/node_modules/grpc/src/client_interceptors.js:1210:9)
at InterceptingListener._callNext (/root/project/node_modules/grpc/src/client_interceptors.js:568:42)
at InterceptingListener.onReceiveStatus (/root/project/node_modules/grpc/src/client_interceptors.js:618:8)
at callback (/root/project/node_modules/grpc/src/client_interceptors.js:847:24)May be related to https://github.com/pulumi/pulumi-kubernetes/pull/925
g
gorgeous-egg-16927
01/08/2020, 5:09 AMYes, that appears to be related to the changes in the latest release. Can you file an issue with a repro if possible?
a
adamant-intern-63433
01/08/2020, 10:55 AMThat’s the error we started getting on multiple projects today.
We’ve been using
k8s.Providerb
busy-umbrella-36067
01/08/2020, 3:18 PMVersion locking the NPM package on 1.4.1 resolved it for me
➕ 1
Opened up https://github.com/pulumi/pulumi-kubernetes/issues/939 to track this
g
gorgeous-egg-16927
01/08/2020, 5:03 PMThanks, looking into it now
@busy-umbrella-36067 I haven’t been able to reproduce the problem locally. Could you update the issue with package versions you’re using, and more details on the workflow where you’re seeing the problem (i.e. using existing stacks, only on new stacks, only on preview, etc.)? Thanks!
b
busy-umbrella-36067
01/08/2020, 6:01 PM@gorgeous-egg-16927 updated the issue,
--skip-previewI lied, getting the issue with
--skip-previewNot sure if you're able to view user stacks on the console: https://app.pulumi.com/mazamats/test/dev/updates/5
g
gorgeous-egg-16927
01/08/2020, 10:33 PMTracked down the problem and am reverting the relevant changes until we can release a proper fix. 1.4.3 release should be out this afternoon with the problematic changes reverted
🙏 2