argocd: Add GPG public key for user import

[drGrove]

No description provided.

[daurnimator]

Although this is useful, its sort of a dangling artifact.
Can we find a better place for it?

[daurnimator]

@drGrove see earlier comment:

I like the current setup that each folder in the root is an app. Can we put the key in the argocd folder? or the root?

[drGrove]

@drGrove see earlier comment:

I like the current setup that each folder in the root is an app. Can we put the key in the argocd folder? or the root?

I think I had it there before. I can put it in the folder, should it be in a subfolder of argocd?

[daurnimator]

I think I had it there before. I can put it in the folder, should it be in a subfolder of argocd?

idea: what about as an annotation/label on the deploy-key resource itself?

or can we get SOPS to not encrypt a specific field?

[drGrove]

I think I had it there before. I can put it in the folder, should it be in a subfolder of argocd?

idea: what about as an annotation/label on the deploy-key resource itself?

or can we get SOPS to not encrypt a specific field?

SOPS will only encrypt fields we tell it to. But normally that's data|stringData.
As far as labels/annotations, they have a max limit which I think this would would blow through