gifted-balloon-26385
12/14/2023, 12:06 AMnew k8s.helm.v3.Chart(
"aws-load-balancer-controller",
{
chart: "aws-load-balancer-controller",
version: "1.6.2",
fetchOpts: {
repo: "<https://aws.github.io/eks-charts>",
},
namespace: "kube-system",
values: {
clusterName: eksCluster.name,
serviceAccount: {
create: false,
name: "aws-load-balancer-controller",
},
},
}
);
This works fine, but I believe the controller automatically updates its own TLS secret, so whenever I run pulumi up
again, it tries to re-replace the changes with the original ones from the helm chart.
Is there a solution or workaround to this?gifted-balloon-26385
12/14/2023, 12:29 AMgifted-balloon-26385
12/14/2023, 12:48 AMdry-keyboard-94795
12/14/2023, 1:06 PMignoreChange
on the secret/certificate's data.
See here for an example of transformations:
https://www.pulumi.com/registry/packages/kubernetes/api-docs/helm/v3/chart/#chart-with-transformationsstale-answer-34162
12/14/2023, 2:46 PMexport const csiAddon = new aws.eks.Addon(
'aws-ebs-csi-driver-addon',
{
clusterName: eksCluster.name,
addonName: 'aws-ebs-csi-driver',
resolveConflictsOnUpdate: 'OVERWRITE',
// addonVersion: 'v1.24.1-eksbuild.1',
},
{ dependsOn: [eksCluster, nodeGroup] },
)