This change will allow user to encode secrets using Bitnami Sealed Secrets tool.
🎤 Context
In case when user publish catalog info to Git, and use secret data as property, this data is visible in Git.
For this issues recommended to use sealed secrets, which are encoded and stored in Git, and decoded already by controller where this secret has to be used.
✌️ Possible Implementation
Proposed to create filter which will encode value using kubeseal utility and GitHub token from integration configuration as encoding key.
To keep this filter extendable proposed to make filter sealing tool changeable from configuration, but currently implemented just for kubeseal
🔖 Feature description
This change will allow user to encode secrets using Bitnami Sealed Secrets tool.
🎤 Context
In case when user publish catalog info to Git, and use secret data as property, this data is visible in Git. For this issues recommended to use sealed secrets, which are encoded and stored in Git, and decoded already by controller where this secret has to be used.
✌️ Possible Implementation
kubesealutility and GitHub token from integration configuration as encoding key.kubeseal