Introduce Helm migration story
See original GitHub issueWe know that there are many benefits from being able to convert Kubernetes YAML, and Helm Charts, to Pulumi, especially to leverage all the benefits of a language. However, it would also be possibly nice to be able to leverage the existing ecosystem of charts. For example:
import * as helm from "@pulumi/helm";
const datadog = new helm.Chart("datadog", {
apiKey: ...,
repository: ...,
});
These would clearly need to be weakly typed, although one could also imagine a world where we use code-gen to create even more first class resource types. Such as
import {Datadog} from "@pulumi/helm-charts";
const datadog = new Datadog({ /* yay, strong typing */ });
Assigning to @hausdorff to think about.
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
A 6-minute introduction to HELM - Medium
You can create different installations of a product, e.g., Redis and have two different releases created and tracked in the cluster.
Read more >Migrating Helm v2 to v3
Migrating Helm v2 to v3. This guide shows how to migrate Helm v2 to v3. Helm v2 needs to be installed and managing...
Read more >Introduction to Helm: Charts, Deployments, & More - Harness
In its current rendition, Helm is a client that is installed outside the Kubernetes cluster. It leverages kubectl to connect and interact with ......
Read more >Migrating from Helm v2 to v3 - Martin Hickey, IBM - YouTube
You want to try Helm v3, but perhaps you already have Helm v2 and need to migrate. We'll look at a migration from...
Read more >Hands-On Helm - YouTube
Introduction to Helm | Kubernetes Tutorial | Beginners Guide · What is Helm in Kubernetes? · How to Build a CLI with Go...
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
From my recent discussions with folks recently, not supporting a Tiller-based provider is actually a good thing anyway. It’s worth tracking how we’d dock in with the new CRD-based Helm system, however.
This can be marked as done. An ancillary note is that it turned out to be hard to write a Tiller provider, so we “just” wrote the Helm adopter.