-
Notifications
You must be signed in to change notification settings - Fork 49
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
并非所有用户都有PVC,建议etcd支持hostPath Volume #522
Comments
@Edwin-Li-01 PVC 确实是为了高可用考虑的,不过也是应该考虑更多灵活场景 👍,我在 Helm 包优化的 issue #347 中补充了这一点,会在新版本中支持 |
@Edwin-Li-01 Hi 我们已经将你提的这些需求加入到了 v0.5.0 Milestone 版本规划中,预计在本月月底正式发布,如果有关于这个版本更好的建议,欢迎在👉论坛👈中留言哈 |
@elliotxx 我认为hostPath不应该直接在helm安装的时候就显式声明,因为sts的workload需要动态去创建,我们无法预知用户需要几个etcd副本. 想要做到动态的hostpath最好的实践方式是使用类似toplvm这样的本地存储CSI方案,karpor里需要做的只是去支持用户动态配置storageClass. 我这边提交了一个pr,麻烦看看KusionStack/charts#50 |
@regend 感谢反馈和贡献!👍 我们先讨论一下,晚点给你反馈 |
用户提的 KusionStack/charts#50 已合并,这个 Issue 先关闭了 |
What would you like to be added?
sts资源etcd 依赖PVC 但未必所有用户的环境能够支持,建议适配支持hostPath Volume,PVC 可以作为高可用的方案建议
Why is this needed?
部署优化
The text was updated successfully, but these errors were encountered: