Please vote on this issue by adding a :thumbsup: reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Tell us about the feature
The problem:
We have backup management within our operator, but to recover from the backup users also need to keep the Secret with users and passwords somewhere, so that restoration is succesful.
We expect users to have a backup mechanism for secrets or have some centralized secret management system.
This becomes a problem especially in cases where the whole Kubernetes cluster fails and users need to provision the environment from scratch.
Proposal:
Remove the need for users to backup secrets. There is no good reason why we can’t perform the restore without users being pre-created.
Community Note
Tell us about the feature
The problem:
We have backup management within our operator, but to recover from the backup users also need to keep the Secret with users and passwords somewhere, so that restoration is succesful.
We expect users to have a backup mechanism for secrets or have some centralized secret management system.
This becomes a problem especially in cases where the whole Kubernetes cluster fails and users need to provision the environment from scratch.
Proposal:
Remove the need for users to backup secrets. There is no good reason why we can’t perform the restore without users being pre-created.
Link to JIRA