Open yasin-kismet opened 2 years ago
Could you please share the diff you get before this error surfaces?
Im also seeing this behaviour
@jaxxstorm When I get this error this is the diff I get if that helps
@jaxxstorm
For relation, I found this thread. https://pulumi-community.slack.com/archives/CRFURDVQB/p1646013705462779?thread_ts=1646013632.251649&cid=CRFURDVQB
I should also mention that this problem doesn't exist with the k8s.helm.v3.Release()
and is how I've worked around it currently, but still exists with k8s.helm.v3.Chart()
As per this issue: https://github.com/pulumi/pulumi-kubernetes/issues/1937
I should also mention that this problem doesn't exist with the
k8s.helm.v3.Release()
and is how I've worked around it currently, but still exists withk8s.helm.v3.Chart()
As per this issue: #1937
@LukeOman That's helped. Thanks.
@LukeOman Thanks, solution work for me
How do we apply transformations in help release?
Any updates on this issue? We are having the same problem but since we're in production with k8s.helm.v3.Chart()
, we cannot easily switch to k8s.helm.v3.Release()
. 😞
It's possible that this will also work with helm.v3.Chart
when Server-side Apply is enabled (will be default in v4 of the provider). You can test it now by setting enableServerSideApply
on the provider config.
Hi, we tried with v4, seems it is still the same case
Same issue here
What happened?
I am trying to deploy 2 different applications on AWS eks using pulumi. If I am applying ingress for the first time, there is no problem, but when I want to make an update, I get the error
ingressclassparams.elbv2.k8s.aws "alb"
already exists.Steps to reproduce
Since my application is a bit complex, I tried to deploy a simple application to a new aws account, but I got the same error.
cluster.ts
Expected Behavior
I would expect the application to deploy smoothly.
Actual Behavior
The pulumi throws the
alb already exists
error after the first deployment.Versions used
Additional context
At first I thought the problem would be with the controller itself and I created an issue, but I guess pulumi is trying to create a new ingress class with the same name while updating something, without deleting the old one.
https://github.com/kubernetes-sigs/aws-load-balancer-controller/issues/2698
Contributing
Vote on this issue by adding a 👍 reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).