https://pulumi.com logo
#general
Title
# general
e

early-match-56268

10/07/2019, 11:30 PM
hey all, I just upgraded to 1.2 and now pulumi is trying to add annotations such as the following to the resources in my k8s cluster
Copy code
~ metadata: {
          + annotations: {
              + <http://pulumi.com/initialApiVersion|pulumi.com/initialApiVersion>: "v1"
            }
        }
this is causing resources to try to update/delete when they have not changed. Is there any way to work around this?
w

white-balloon-205

10/07/2019, 11:31 PM
Just to confirm: * CLI upgrade or one or more package upgrades? * From what versions?
e

early-match-56268

10/07/2019, 11:36 PM
Copy code
"@pulumi/kubernetes": {
-            "version": "1.1.0",                                                                                                                                                                                                            -            "resolved": "<https://registry.npmjs.org/@pulumi/kubernetes/-/kubernetes-1.1.0.tgz>",                                                                                                                                                                                                                                                     +            "version": "1.2.0",                                                                                                                                                                                                            +            "resolved": "<https://registry.npmjs.org/@pulumi/kubernetes/-/kubernetes-1.2.0.tgz>",
1.1 -> 1.2 both k8s package and cli
also google protobuf package was upgraded from 3.9.2 to 3.10.0
w

white-balloon-205

10/07/2019, 11:50 PM
Might need @gorgeous-egg-16927's eyes on this one.
w

worried-city-86458

10/07/2019, 11:50 PM
I went through this upgrade. It's just adding an annotation, so "mostly harmless".
e

early-match-56268

10/07/2019, 11:51 PM
yea most are fine, but a few are causing a replace
i tried downgrading back to 1.1 but still seeing the same issue which is strange so maybe something else is going on.
is it possible to just manually update the stack and add these annotations? for most resources i am fine with recreating but a couple i would like to not have to recreate
c

creamy-potato-29402

10/08/2019, 12:24 AM
@early-match-56268 this should not cause replacements. could you post the complete diff so we can take a look?
e

early-match-56268

10/08/2019, 2:27 PM
So it ended up being a couple issues that were causing the replacements. First, a namespace update was triggering a replacement of secrets that depended on that namespace, which then triggered the replacements of helm charts that were using those secrets. Second was a storage class update which triggered the replacement of helm charts using that storage class. I manually updated the namespace and the storage class to include the annotation and now everything is just a clean update.
👍 1