-
Notifications
You must be signed in to change notification settings - Fork 408
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
install error #202
Comments
看起来默认的storageclass供应方案和您已安装的local-path-provisioner冲突了。
|
k get storageclass -A helm install sreworks ./ --create-namespace --namespace sreworks --set global.accessMode="nodePort" --set appmanager.home.url="http://127.0.0.1:30767" --set saas.onlyBase=true --set global.storageClass="local-path" |
my k8s create by rancher desktop on mac m1, after delete storageClass、clusterrole,i can install,but: k logs sreworks-core-init-job-7fnkn -n sreworks
k logs sreworks-appmanager-cluster-initjob-lbk7r -n sreworks During handling of the above exception, another exception occurred: Traceback (most recent call last): curl http://127.0.0.1:30767/ |
不好意思,还差个参数
|
先看一下内置mysql是否起来,然后appmanager这个pod有没有running。这里大概需要等待5-10分钟左右。在appmanager pod running了之后,这个sreworks-core-init-job才能够成功注入底座应用。如果还有问题。麻烦kubectl get pod -nsrewors截取贴一下。 |
my k8s version is v1.25.6+k3s1
error message:
helm install sreworks ./ --create-namespace --namespace sreworks --set global.accessMode="nodePort" --set appmanager.home.url="http://127.0.0.1:30767" --set saas.onlyBase=true
Error: INSTALLATION FAILED: rendered manifests contain a resource that already exists. Unable to continue with install: ClusterRole "local-path-provisioner-role" in namespace "" 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 "sreworks"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "sreworks"
The text was updated successfully, but these errors were encountered: