• saowu

    • 发布 #29 
    client.go:134: [debug] creating 1 resource(s)
install.go:160: [debug] CRD storageclasscapabilities.storage.kubesphere.io is already present. Skipping.
client.go:134: [debug] creating 1 resource(s)
install.go:160: [debug] CRD workspaces.tenant.kubesphere.io is already present. Skipping.
client.go:134: [debug] creating 1 resource(s)
install.go:160: [debug] CRD workspacetemplates.tenant.kubesphere.io is already present. Skipping.
Error: rendered manifests contain a resource that already exists. Unable to continue with install: GlobalRole "authenticated" 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 "ks-core"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "kubesphere-system"
helm.go:84: [debug] GlobalRole "authenticated" 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 "ks-core"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "kubesphere-system"
rendered manifests contain a resource that already exists. Unable to continue with install
helm.sh/helm/v3/pkg/action.(*Install).RunWithContext
	helm.sh/helm/v3/pkg/action/install.go:320
main.runInstall
	helm.sh/helm/v3/cmd/helm/install.go:286
main.newUpgradeCmd.func2
	helm.sh/helm/v3/cmd/helm/upgrade.go:130
github.com/spf13/cobra.(*Command).execute
	github.com/spf13/cobra@v1.6.1/command.go:916
github.com/spf13/cobra.(*Command).ExecuteC
	github.com/spf13/cobra@v1.6.1/command.go:1044
github.com/spf13/cobra.(*Command).Execute
	github.com/spf13/cobra@v1.6.1/command.go:968
main.main
	helm.sh/helm/v3/cmd/helm/helm.go:83
runtime.main
	runtime/proc.go:250
runtime.goexit

    求助，在host重新安装4.1.2失败了，好像是v3.4.1没有卸载干净

      • frezesK零S

        • 发布 #30

        saowu

        删掉冲突的资源重试下呢？

        这个资源理应该跟随 3.x 版本的helm charts 一起卸载，后续是否有手动变更，导致资源清单中 annotation 缺少特定annotation，charts 卸载时未被删除。

        所以可以直接kubectl delete cluserrole authenticated 删除，如果阻塞，可以看下是否有finalizers 字段，edit 将finalizers 字段移除置空。

            • saowu

              • 发布 #31

              frezes

              谢谢大佬，我运行了kubesphere-delete.sh脚本，发现卡在了删除crd环节，Terminating 状态通常由 ‌Finalizers 未完成清理‌ 导致，运行如下命令恢复

              kubectl patch crd/pipelines.devops.kubesphere.io --type=merge -p '{"metadata":{"finalizers":[]}}'

                请问，新版本的 示例 应用 bookinfo 自带的镜像 都是 examples-bookinfo-xxx-v1:1.10.1 版本，拉取不到镜像了(v1:1.20.2 版本可以拉取) , 除了直接去编辑pod的yaml里image配置，还有什么更好的办法解决吗？

                • saowu

                  • 发布 #33

                  安装插件卡住了，咋办

                  请问在v4.1.2中添加EKS集群时，点击创建以后无反应，应该如何解决呢？

                  在网页的控制台上查看错误信息为：

                  Get “https://DA11ED6DEE5E65501CC969D43CC12F59.gr7.us-west-2.eks.amazonaws.com/api/v1/namespaces/kube-system?timeout=10s”: getting credentials: exec: executable aws not found

                  It looks like you are trying to use a client-go credential plugin that is not installed.

                  To learn more about this feature, consult the documentation available at:

                  https://kubernetes.io/docs/reference/access-authn-authz/authentication/#client-go-credential-plugins

                  执行下面命令 kubectl logs -n kubesphere-system ks-apiserver-686ddff57b-b99p4 得到的输出如下：

                  I0311 10:33:58.757629 1 filters.go:96] undefined - “GET /apis/cluster.kubesphere.io/v1alpha1/clusters/e HTTP/1.1” 404 232 3ms

                  I0311 10:33:59.190569 1 filters.go:96] undefined - “GET /apis/cluster.kubesphere.io/v1alpha1/clusters/eks HTTP/1.1” 404 236 3ms

                  I0311 10:34:01.698486 1 filters.go:96] undefined - “GET /apis/cluster.kubesphere.io/v1alpha1/clusters/eks HTTP/1.1” 404 236 3ms

                  E0311 10:34:36.135942 1 utils.go:65] /workspace/pkg/kapis/cluster/v1alpha1/handler.go:155 Get “https://56E7C1D89789B8E362CEE8E2094B0372.gr7.us-west-2.eks.amazonaws.com/api/v1/namespaces/kube-system?timeout=10s”: getting credentials: exec: executable aws not found

                  It looks like you are trying to use a client-go credential plugin that is not installed.

                  To learn more about this feature, consult the documentation available at:

                  https://kubernetes.io/docs/reference/access-authn-authz/authentication/#client-go-credential-plugins

                    hongming
                    谢谢！

                    按照这个教程后，我执行了下面的操作：
                    在主集群的服务器，配置了aws credentials，然后执行了
                    aws eks --region us-west-2 update-kubeconfig --name xxxxxx

                    kubectl config use-context kubernetes-admin@cluster.local # 不执行这个，后面会报错

                    cat <<EOF >kubesphere-secret.yaml apiVersion: v1 kind: Secret metadata: name: kubesphere namespace: kubesphere-system annotations: kubernetes.io/service-account.name: "kubesphere" type: kubernetes.io/service-account-token EOF

                    kubectl apply -f kubesphere-secret.yaml
                    TOKEN=`kubectl -n kubesphere-system get secret kubesphere -o jsonpath='{.data.token}' | base64 -d` kubectl config set-credentials kubesphere --token=${TOKEN}
                    kubectl config set-context --current --user=kubesphere

                    最后得到了如下的config（删减了一些其他信息）

                    apiVersion: v1

                    clusters:

                    - cluster:

                    certificate-authority-data: LS0tLS1CR【省略】

server: https://【省略】.gr7.us-west-2.eks.amazonaws.com

                    name: arn:aws:eks:【省略】:cluster/pageguo

                    contexts:

                    - context:

                    cluster: arn:aws:eks:【省略】:cluster/pageguo

user: kubesphere

                    name: arn:aws:eks:【省略】:cluster/pageguo

                    current-context: arn:aws:eks:【省略】:cluster/pageguo

                    kind: Config

                    preferences: {}

                    users:

                    - name: arn:aws:eks:【省略】:cluster/pageguo

                    user:

                    exec:

  apiVersion: client.authentication.k8s.io/v1beta1

  args:

  - --region

  - us-west-2

  - eks

  - get-token

  - --cluster-name

  -【省略】

  command: aws

  env: null

  interactiveMode: IfAvailable

  provideClusterInfo: false

                    - name: kubesphere

                    user:

                    token: eyJhbGciOiJSU【省略】

                    将上面的config添加到控制台以后，现在在网页控制台Network里提示：

                    Unauthorized

                    然后我执行了下面的命令：
                    kubectl logs -n kubesphere-system ks-apiserver-686ddff57b-b99p4

                    得到了如下的输出

                    error: You must be logged in to the server (Unauthorized)

                    我怀疑是EKS上没有安装Kubesphere导致的。但是我看帖子里都讲，现在不需要在EKS里安装KubeSphere了。尤其是在执行kubectl apply -f kubesphere-secret.yaml的时候，当前的context应该是哪个？

                      xiaotian

                      在aws eks上卸载3.x版本ks，没有完全卸载。手动删除ns也删除不掉

                      在这种情况下增加集群成员时出现timeout

                          • saowu

                            • 发布 #38

                            quinniup

                            命名空间可能有Finalizers，可以清理一下；

                            我卸载之前也没卸干净，去官网找的kubesphere-delete.sh清理的，个别crd也有Finalizers