nacos-k8s
nacos-k8s copied to clipboard
helm部署的nacos集群是否能再完善些?
Dear,
目前测试下来使用helm部署的nacos cluster目前还不太完善,部署会有一些报错,另外mysql部署使用的还是replicationcontrollers的模式,这种在k8s中已经被Deployment的模式淘汰了,一直关注Nacos的发展,希望它各方面都比较好,如果您比较忙,我可以提供一些helm部署的方式,并没恶意,只是想nacos更好!O(∩_∩)O~
这个当然特别欢迎共建的,这哪里有恶意,哈哈,如果有想法可以直接改,我目前是在弄opreator的形式来进行nacos部署
欢迎提出pr,这是开源项目,我也只有一个人维护,所以特别希望大家一起贡献,去壮大nacos
原来就你一个人维护啊 那难怪了!
我看看 AWS 上怎么部署最方便
helm部署报错如下: Release "physical-history" failed and has been uninstalled: rendered manifests contain a resource that already exists. Unable to continue with install: Service "nacos-cs" in namespace "helm" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key "app.kubernetes.io/managed-by": must be set to "Helm"; annotation validation error: missing key "meta.helm.sh/release-name": must be set to "physical-history"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "helm"