ConfigGroup and renderYamlToDirectory provider
See original GitHub issueMight be more of a question, is an explicit provider with renderYamlToDirectory
supported?
If so, it’s not working and this is a bug 😃
Pulumi: v3.10.1 kubernetes: 3.7.0
This is in the context of a ConfigGroup with transformations if it matters.
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (4 by maintainers)
Top Results From Across the Web
renderYamlToDirectory fails when kubeconfig is empty #992
Problem description Hi, I'm trying to use renderYamlToDirectory which was ... pulumi:providers:kubernetes resource 'foo-us-west1's property ...
Read more >Migrating From Kubernetes YAML or Helm Charts - Pulumi
ConfigFile : deploy a single Kubernetes YAML file; ConfigGroup : deploy a ... set the renderYamlToDirectory property on an explicit Kubernetes provider ......
Read more >Pulumi kubernetes ConfigGroup takes string, I only got Outputs
Any time you're needing to use an output value inside a string, you'll need to make sure the output is resolved using an...
Read more >Manage Kubernetes clusters using the Civo Pulumi provider
Once the cluster is ready and the Kubernetes provider is configured, we will use Pulumi's k8s.yaml.ConfigGroup object to deploy Ambassador's ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
If you already have
$KUBECONFIG
environment variable set, the provider by default will read it and have a truthykubeconfig
value.The workaround is to explicitly set
kubeconfig: ""
@lamson , thanks for that, that was the exact problem.
Much appreciated.