No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

image.png

Hello folks, i'm upgrading my pulumi-eks package but i'm getting errors when doing `pulumi up`  =&gt;
``` ~   ├─ kubernetes:<http://helm.sh/v3:Release|helm.sh/v3:Release>  rh-notification                     **updating failed**     [diff: ~checksum]; 1 error```

``` kubernetes:<http://helm.sh/v3:Release|helm.sh/v3:Release> (rh-notification):
    error: 1 error occurred:
    	* Helm release "rh-staging/rh-notification" failed to initialize completely. Use Helm CLI to investigate.: failed to become available within allocated timeout. Error: Helm Release rh-staging/rh-notification: failed to replace object: Service "rh-notification" is invalid: spec.loadBalancerClass: Invalid value: "null": may not change once set```

just bumped the package, so there is a breaking change or something ?

ok i was able to fix the issue by adding in my service.yaml
``` <http://service.beta.kubernetes.io/aws-load-balancer-nlb-target-type|service.beta.kubernetes.io/aws-load-balancer-nlb-target-type>: instance 
....
loadBalancerClass: service.k8s.aws/nlb```

but in the documentation they say it's the default value, <https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.6/guide/service/nlb/#configuration> so i don't get why i got this error after upgrading pulumi packages ? :thinking_face: