wireguard-operator VS vault-secrets-operator

Why wouldn’t this just work? kubectl debug node/ -it —image=busybox:latest Or a wireguard/OpenVPN operator something like https://github.com/jodevsa/wireguard-operator ? Just feels like a solution searching for a problem. That said if this is just a side project for your own experience/fun then more power to you!

I'd also recommend to look into existing controllers/operators like wireguard-operaror to see how others solved that problem.

For home use, I wouldn't bother with Vault unless that's really what you want to learn. Then it's worth looking into setting something up where you could use vault secrets, using one of the available options (I haven't seen the vault-secrets-operator being mentioned).

It is but it affects vault-secrets-operator too, see https://github.com/ricoberger/vault-secrets-operator/issues/104 (and no, I’ve only use vault-secrets-operator)

If you are using an external KMS in any case, then there are other options, such as the kubernetes-external-secrets operator that was originally started by GoDaddy and the externalsecret-operator from Container Solutions. If you use HashiCorp Vault, you also have the option of using the Vault Secrets operator. This works similarly to the Sealed Secrets Operator, but instead of managing its own key material, it retrieves the secrets from Vault. The CNCF Technology Radar from January 2021 provides an overview of the types of tools that are available for secrets management.