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

if so, you can  `import` it. but if not, the solution is not Pulumi-specific - you can just use whatever programming language you are using to run the equivalent command as `kubectl annotate`

The pulumi ID is the `[namespace/]name` of the resource.

Thanks!  kind of cumbersome that you need to sync up the declared resource config exactly with the config of the existing resource.  In this case, that means figuring out all the fields of the SA, which you may not care about or even want managed by Pulumi

just some feedback there.  In this case, I just want to "import" the *annotation of the service account*, meaning I only want Pulumi to track and care about changes to that field of the existing resource