Hi guys,

I've been reading the docs I found and got to this PR which is great to improve the documentation.

What about to include more details about a case of disaster of a K8s cluster 🤔

I've been testing the sealed secrets and I've considering use its key renewal but faced to some steps which I've doubts, some of them:

• need to re-encrypt everything and I don't know a good way to do it to many secrets once it looks like I'll have to automate it to find all the secrets on kubernetes and re-encrypt it right ? or there is a flag ?

• If I would like to create my own key and not renew it can I do that ? Would I have this flexibility ? I considered it after not know what to do in case I lose my whole cluster and don't have all the keys which was lost in the broken cluster. So if I have my own key it won't be a problem to encrypt, decrypt and launch a new cluster which can decrypt my sealedsecrets to the cluster from github whith Fluxcd.

bors r+

@weslleycamilo sure, disaster recovery is important and I'd surely like to improve the docs and/or the feature set to make disaster recovery more approachable.

Would you mind creating an issue for that; it's hard to have a good discussion in a non directly related PR that is about to be merged and thus closed.

sure @mkmik. Thank you for your feedback.

Build succeeded

• continuous-integration/travis-ci/push