Create a process for ad hoc authentications

1. Create a source without having a parent
2. Would have no availability status
3. Would not ( this design ) show up in the UI
4. Specify resource type as "Account" or "Tenant" ( leaning towards account )
5. Kind of single user ( not attached to a resources ( or source resources )
6. Document how to create and consume these authentications
7. Requirement: You MUST be incluster and we will send the authentications back decrypted ( in cluster only )

Backed by this request:

looking for a solution to store customer credentials, for Notifications they may need to store passwords for their webhooks or other secrets (integration with Splunk, Slack...)

Do you have a solution for anything like this?

Design Doc: https://docs.google.com/document/d/1dokYxzbqIAQrG7UYK17zROy4QTSnTwGgQifMWbjQ7VU/edit#