velero VS Vault

Openshift last I looked used Velero under the covers for the functionality, which works fine in standard kubernetes. Most if not all that Openshift does is Open source.

Valero

velero is also a popular solution to for k8s backup that is 3rd party you might check out.

Logical backups using pre and post hooks thanks to this suggestion https://github.com/vmware-tanzu/velero/issues/2763 working way better than kanister blueprints.

While not discounting OP or the work in this repo (seems like a fun k8s/go project), folks might check out Velero for this purpose if they're looking to rely on this kind of export in prod: https://github.com/vmware-tanzu/velero

Hyper-V itself does not directly support backing up container-based platforms like Kubernetes clusters. To back up a Kubernetes cluster, you would typically use tools that interact with the Kubernetes API to capture the necessary data and metadata for backup purposes. Some of those tools are Velero https://velero.io/ (formerly Heptio Ark), Kasten K10, and Stash.

For Kubernetes-land, https://velero.io/ is awesome - but I haven't used it for online-database backups yet. If you're exploring, I'd checkout Velero - if you just need something to work reliably, I'd checkout Percona.

If you're looking for a backup solution for managed kubernetes, check out Velero. It is great for non-managed kube as well (but you've got other options like etcd backups)

You can also leverage https://velero.io/ to backup both cluster state and pvc state to s3

HashiCorp Vault

For a more comprehensive and robust secret management solution, get your hands on tools like GCP Secret Manager, or HashiCorp Vault. They're like the security guards of your secrets, providing a safe house, access control, and keeping logs of who’s been snooping around.

HashiCorp Vault is a popular tool for managing secrets in Kubernetes clusters. It offers advanced features such as secure storage, encryption, dynamic secrets generation, and integration with Kubernetes through its Kubernetes authentication method.

So you've just bought a new platform tool? Maybe it's Hashicorp Vault? Snyk? Backstage? You’re excited about all of the developer experience, security and other benefits you're about to unleash on your company—right? But wait…

You seem to be looking for a cross-platform solution, and https://www.vaultproject.io/ provides just that. If everything was in AWS, AWS Secret Manager might be great, but imo Vault provides much better platform-agnostic capabilities.

https://github.com/openwrt/luci/blob/master/applications/luc...

https://developer.hashicorp.com/vault/tutorials/secrets-mana... https://github.com/hashicorp/vault :

> Refer to Build Certificate Authority (CA) in Vault with an offline Root for an example of using a root CA external to Vault.

Secret Management: Securely stores sensitive configuration data and secrets using tools like AWS Secrets Manager or HashiCorp Vault. Avoid hardcoding secrets in code or configuration files.

The author of this tool basically took the Shamir code from Hashicorp Vault, which is pretty mainstream. If you're looking for a solid implementation, I would start there[0]. I wouldn't use the Shamir code from this repo, as it's an old version of the vault code using field arithmetic that doesn't run in constant time.

[0]: https://github.com/hashicorp/vault/blob/main/shamir/shamir.g...

Out of curiosity, what do you mean by this? cross-cluster? they already have HA: https://github.com/hashicorp/vault/blob/v1.14.1/website/cont...

while digging up that link, I also saw one named replication: https://github.com/hashicorp/vault/blob/v1.14.1/website/cont...