-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
关于架构设计的几个疑问? #3
Comments
取决于实际需求。之前计划是兼容Vault API的,否则替换Vault比较难。因为在K8s体系中用Vault,和在其他传统环境中用KMS,API也区别较大。所以一个可能比较合理的方式是在daemon那个环节对Vault API进行支持
没有…… |
@InfoHunter 我们实际的场景上直接基于client/sdk/api使用vault比较少,而且也比较麻烦,一般都是通过第三方工具完成秘钥从后端到容器内部的同步,因此如果能考虑第二点还是很有益处的。 |
@TommyLike 你使用的第三方工具是哪个? |
Vault kubernetes sidecar https://developer.hashicorp.com/vault/docs/platform/k8s/injector |
这个我理解不用特殊处理,就是如果RustyVault可以兼容Vault的API的话,则还可以继续使用这个injector,从而实现对用户无感切换 |
可能除了API,还得包括config.hcl这些配置文件格式的兼容 |
The text was updated successfully, but these errors were encountered: