我问这个问题对谷歌库集团和这是最好的回应:
1) Under normal circumstances, does the Vault stay in an unsealed state? I believe it would as a dynamically provisioned server should not have to coordinate an unseal.
是。一旦Vault被初始化并且被解除密封,它通常处于未密封状态。
2) Is the purpose of sealing to off-board staff to rotate keys and in case of an intrusion?
跳马的密封使交钥匙机制来停止所有的服务库的 。这将需要特定数量的开封密钥持有者到 才能使保险库再次运作。
3) What's the best practice for ensuring the vault process is always running, since if it dies the Vault will seal? Also, in a highly available configuration, if one Vault node's process dies, does it seal the Vault for everyone?
有这个没有官方的最佳实践建议。但 在专用实例/群集中运行保险柜,其中 的内存受限/无法访问。使用 后端以HA模式运行Vault是很好的。如果任何集群节点进入 关闭或者Vault进程重新启动,它将处于密封的 状态,并且需要执行非密封操作才能使其运行 。
最好的, Vishal