• DevOps
  • 通过AWS EKS 安装的v4.1.3, host主集群显示Devops未安装的问题

创建部署问题时,请参考下面模板,你提供的信息越多,越容易及时获得解答。
发帖前请点击 发表主题 右边的 预览(👀) 按钮,确保帖子格式正确。
你只花一分钟创建的问题,不能指望别人花上半个小时给你解答。

操作系统信息
AWS EKS

Kubernetes版本信息

1.32

容器运行时
使用 docker/containerd,版本多少

KubeSphere版本信息
v4.1.3。通过已建好的EKS集群 使用Kubernetes 快速安装。

问题是什么
启用Devops扩展组件之后,host集群无法创建。

    apiVersion: kubesphere.io/v1alpha1

    kind: InstallPlan

    metadata:

      annotations:

        kubesphere.io/creator: admin

      creationTimestamp: “2025-04-11T01:23:18Z”

      finalizers:

      - kubesphere.io/installplan-protection

      generation: 13

      name: devops

      resourceVersion: “366386”

      uid: 3396ea97-352a-43fe-9464-1cf65a1103c4

    spec:

      clusterScheduling:

        placement:

          clusters:

          - host

      config: |+

        extension:

          apiserver:

            replicas: 1

            resources:

              limits:

                cpu: 500m

                memory: 1024Mi

              requests:

                memory: 128Mi

                cpu: 100m

        agent:

          apiserver:

            replicas: 1

            resources:

              limits:

                cpu: 500m

                memory: 1024Mi

              requests:

                memory: 128Mi

                cpu: 100m

          controller:

            replicas: 1

            resources:

              limits:

                cpu: 500m

                memory: 1024Mi

              requests:

                cpu: 100m

                memory: 128Mi

          jenkins:

            securityRealm:

              openIdConnect:

                # The kubesphere-core api used for jenkins OIDC

                # If you want to access to jenkinsWebUI, the kubesphereCoreApi must be specified and browser-accessible

                # Modifying this configuration will take effect only during installation

                # If you wish for changes to take effect after installation, you need to update the jenkins-casc-config ConfigMap, copy the securityRealm configuration from jenkins.yaml to jenkins_user.yaml, save, and wait for approximately 70 seconds for the changes to take effect.

                kubesphereCoreApi: “http://ks-apiserver:30880

                # The jenkins web URL used for OIDC redirect

                jenkinsURL: “http://devops-jenkins:30180

            Master:

              resources:

                requests:

                  cpu: 0.5

                  memory: 6Gi

                limits:

                  cpu: 2

                  memory: 6Gi # recommend set same as requests.memory

              # smtp server settings for notification

              smtp:

                EMAIL_SMTP_HOST: “mail.example.com”

                EMAIL_SMTP_PORT: “465”

                EMAIL_USE_SSL: false

                EMAIL_FROM_NAME: “KubeSphere”

                EMAIL_FROM_ADDR: “admin@example.com

                EMAIL_FROM_PASS: “P@ssw0rd”

              # sonarQube settings

              sonarqube:

                serverUrl: ""

                authToken: ""

            persistence:

              size: 16Gi

              storageClass: ""

              accessMode: ReadWriteOnce

            kubeconfigEnabled: true

      enabled: true

      extension:

        name: devops

        version: 1.1.1

      upgradeStrategy: Manual

    status:

      clusterSchedulingStatuses:

        host:

          conditions:

          - lastTransitionTime: “2025-04-11T01:23:55Z”

            message: ’Release “devops-agent” failed: client rate limiter Wait returned

              an error: context deadline exceeded’

            reason: InstallFailed

            status: “False”

            type: Installed

          - lastTransitionTime: “2025-04-11T01:23:52Z”

            message: The extension agent has been successfully initialized.

            reason: Initialized

            status: “True”

            type: Initialized

          configHash: 27c44748d145f42a

          jobName: helm-install-devops-agent-jwcwgq

          releaseName: devops-agent

          state: InstallFailed

          stateHistory:

          - lastTransitionTime: “2025-04-11T01:23:52Z”

            state: Preparing

          - lastTransitionTime: “2025-04-11T01:23:52Z”

            state: Installing

          - lastTransitionTime: “2025-04-11T01:23:55Z”

            state: InstallFailed

          targetNamespace: kubesphere-devops-system

          version: 1.1.1

      conditions:

      - lastTransitionTime: “2025-04-11T01:23:20Z”

        message: Install complete

        reason: InstallSuccessful

        status: “True”

        type: Installed

      - lastTransitionTime: “2025-04-11T01:23:18Z”

        message: The extension devops has been successfully initialized.

        reason: Initialized

        status: “True”

        type: Initialized

      configHash: 27c44748d145f42a

      enabled: true

      jobName: helm-install-devops-jmw9g5

      releaseName: devops

      state: Installed

      stateHistory:

      - lastTransitionTime: “2025-04-11T01:23:18Z”

        state: Preparing

      - lastTransitionTime: “2025-04-11T01:23:19Z”

        state: Installing

      - lastTransitionTime: “2025-04-11T01:23:20Z”

        state: Installed

      targetNamespace: kubesphere-devops-system

      version: 1.1.1

      商业产品与合作咨询