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 I’m understanding this correctly, it was discussed here <https://pulumi-community.slack.com/archives/CRFURDVQB/p1580204949047000>

the thread concludes that it’s not a security issue because having access to viewing the labels (describing the secret) implies that you have access to viewing the value (getting the secret)

I see. I’m not sure why it hasn’t been changed though, regardless of if the annotation is encrypted or not.

Having secrets output because you do a describe seems horrible.

I tend to agree :slightly_smiling_face: there was some discussion in <https://github.com/pulumi/pulumi-kubernetes/issues/965> which was linked from the thread

if that doesn’t satisfy, I hope we can have a new discussion in the issue you just created :smile:

I just commented on the issue I created with a valid reason for this to be changed