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

The `data` field should be base64 encoded. You can use the `stringData` field if you want to pass in a raw string, and it will get encoded server-side.

I didn't have to do that on my coredns one to get it to work.

image.png

Oh, I’m sorry. I just realized you said this was a ConfigMap, not a Secret. Disregard my previous comment

You should be able to tell what the difference is from the detailed diff when you run `pulumi up`. Likely whitespace, or similar, so copy-paste works well to match the fields exactly.

That sort of worked on the coredns configMap, it isn't working on this one.

Importing the manifest that I posted above should allow you to try it out. I can't make it work and I'm not sure why Pulumi is saying they aren't the same.

Screen Shot 2020-04-08 at 3.29.13 PM.png

```    metadata:{
        annotations: {},
        name: "nginx-nginx-ingress-controller",
        labels: {"k8s-app": "nginx-ingress-controller"},
        namespace:"kube-system"
    },```

Opened <https://github.com/pulumi/pulumi-kubernetes/issues/1065> to track this issue. I’m not sure why it’s requiring that.

Mine didn't show that annotations: {} were missing in red like yours did

I see it now..  Too much thrashing around from the first missing `annotations: {}` had me and pulumi not comparing the same things

I re-imported my manifest, and cleaned up the pulumi .ts with the `annotations: {}` in it, and it worked as expected. Thank you once again <@UE1LN7A22>!!