@sg4i kubectl get repository extensions-museum -o yaml 看看同步状态

  • sg4i 回复了此帖

    阿里云ACK上什么时候可以支持部署V4啊？

    我现在3.4.1 版本有20个集群添加纳管了，按照这个升级，我需要一个一个解绑之后，那人员权限组织呢，也需要重新配置吗？有没有什么好的办法进行升级呢

    5 天 后
    3 个月 后

    请问下，我从3.4.1升级到4.1.2成功后，想将k8s也升级从1.26.5升级到1.30.6。修改了config-sample.yaml
    通过./kk upgrade -f config-sample.yaml -a kubesphere-4.1.2.tar.gz进行升级，提示错误如下，这是为什么？我应该如何升级呢？

    7 天 后

    “Reconciler error” err=<failed to reconcile cluster mainland: failed to install KS Core in cluster mainland: unable to build kubernetes objects from release manifest: resource mapping not found for name: “restart-extensions-museum” namespace: “kubesphere-system” from "": no matches for kind “CronJob” in version “batch/v1beta1” ensure CRDs are installed first> controller=“cluster” controllerGroup=“cluster.kubesphere.io” controllerKind=“Cluster” Cluster=“mainland” namespace="" name=“mainland” reconcileID=“7f29ac92-f2bb-4c8e-ba58-b7eddc117fb5”

    真的要迷死了，不知道怎么处理，v4加入member集群，host集群ks-controller-manager报出的异常。

      quinniup

      • TKE 1.30.0-tke.5
      • containerd 1.6.9
        6 天 后

        • saowu

          • 发布 #28

          什么时候出无痛升级，生产环境这样风险太高了

          13 天 后

          • 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配置，还有什么更好的办法解决吗？