salmon-musician-36333
04/23/2023, 5:57 PM@pulumi/kubernetes
helm.v3.Chart
and @pulumi/eks
Cluster
for this purpose. Looking at the docs, I'm not seeing a way that I can pass the Cluster
to helm.v3.Chart
, rather that it will be running the chart against whatever cluster is helm
default on my system at the time. Is there a way to point it at the cluster I've just created without having to first set up the EKS cluster, then make it default in my shell, and then run the charts deploy?
PS One of the charts I want to deploy is the AWS EFS CSI driver, going by the note on https://www.pulumi.com/blog/persisting-kubernetes-workloads-with-amazon-efscsi-volumes-using-pulumi-sdks/ that it's recommended to use the sigs chart for this. Is that still the case?billowy-army-68599
04/23/2023, 6:01 PMsalmon-musician-36333
04/23/2023, 6:16 PMhelm.v2.Chart
that will work for v3
as well: https://github.com/pulumi/pulumi-kubernetes{
providers: { kubernetes: eksCluster.provider },
dependsOn: [eksCluster, istioIngress],
},
error: Error: invocation of kubernetes:helm:template returned an error: failed to generate YAML for specified Helm chart: could not get server version from Kubernetes: Get "...": x509: certificate is not valid for any names, but wanted to match ...