• 安装部署
  • v3.3.2 ,目前docker hub无法使用,镜像无法拉取

我在 ClusterConfiguration 添加了

imageRegistry:
localRegistry: "registry.cn-beijing.aliyuncs.com" # 添加这一行来设置本地镜像仓库地址

“同时删除 cc status 中的组件状态“,这个要怎么操作?调整enabled?把enabled:true

改成flase ,还是怎么说?

    Cauchy 我在 ClusterConfiguration 添加了

    imageRegistry:
    localRegistry: "registry.cn-beijing.aliyuncs.com" # 添加这一行来设置本地镜像仓库地址

    “同时删除 cc status 中的组件状态“,这个要怎么操作?调整enabled?把enabled:true

    改成flase ,还是怎么说?

    我也在关注这个问题,很久以前部署了一套使用测试环境,自从dockhub无法访问后,每次启动都得走梯子拉取一下镜像才能正常启动,考虑到当前的国内环境,实际环境中没办法完成用

      youyou

      制作离线包,使用内置离线仓库,或者在环境中维护一个harbor ?

      rp492262097
      可以直接删掉多个组件中的这一行,重启ks-installer 触发部署流程,这样部署时修改使用自定义的镜像地址

        frezes

        删除多个组件中的这一行enabled行,启动过程中会报错:

        task devops status is failed (6/7)

        错误如上图,我的配置如下,您这边能不能提供一下修改完的模板?或者帮我改一下,下面是我的ClusterConfiguration配置,我值加了本地镜像地址,没有删除组件状态

        apiVersion: installer.kubesphere.io/v1alpha1
        kind: ClusterConfiguration
        metadata:
          labels:
            version: v3.3.2
          name: ks-installer
          namespace: kubesphere-system
        spec:
          alerting:
            enabled: false
          auditing:
            enabled: false
          authentication:
            jwtSecret: ''
          common:
            core:
              console:
                enableMultiLogin: true
                port: 30880
                type: NodePort
            es:
              basicAuth:
                enabled: false
                password: ''
                username: ''
              data:
                volumeSize: 20Gi
              elkPrefix: logstash
              externalElasticsearchHost: ''
              externalElasticsearchPort: ''
              logMaxAge: 7
              master:
                volumeSize: 4Gi
            gpu:
              kinds:
                - default: true
                  resourceName: nvidia.com/gpu
                  resourceType: GPU
            minio:
              volumeSize: 20Gi
            monitoring:
              GPUMonitoring:
                enabled: false
              endpoint: 'http://prometheus-operated.kubesphere-monitoring-system.svc:9090'
            openldap:
              enabled: true
            redis:
              enabled: false
          devops:
            enabled: true
            jenkinsJavaOpts_MaxRAM: 2g
            jenkinsJavaOpts_Xms: 512m
            jenkinsJavaOpts_Xmx: 512m
            jenkinsMemoryLim: 2Gi
            jenkinsMemoryReq: 1500Mi
            jenkinsVolumeSize: 8Gi
            sonarqube:
              externalSonarToken: 9803da63baa9610526a9c26aca0cc9204f9dcfb1
              externalSonarUrl: 'http://10.83.100.114:31582'
          edgeruntime:
            enabled: false
            kubeedge:
              cloudCore:
                cloudHub:
                  advertiseAddress:
                    - ''
                  nodeLimit: '100'
                cloudhubHttpsPort: '10002'
                cloudhubPort: '10000'
                cloudhubQuicPort: '10001'
                cloudstreamPort: '10003'
                nodeSelector:
                  node-role.kubernetes.io/worker: ''
                service:
                  cloudhubHttpsNodePort: '30002'
                  cloudhubNodePort: '30000'
                  cloudhubQuicNodePort: '30001'
                  cloudstreamNodePort: '30003'
                  tunnelNodePort: '30004'
                tolerations: []
                tunnelPort: '10004'
              enabled: false
              iptables-manager:
                enabled: true
                mode: external
          etcd:
            endpointIps: 10.83.100.114
            monitoring: false
            port: 2379
            tlsEnable: true
          events:
            enabled: false
          logging:
            containerruntime: docker
            enabled: true
            logsidecar:
              enabled: true
              replicas: 2
          metrics_server:
            enabled: true
          monitoring:
            gpu:
              nvidia_dcgm_exporter:
                enabled: false
            storageClass: ''
          multicluster:
            clusterRole: none
          network:
            ippool:
              type: none
            networkpolicy:
              enabled: true
            topology:
              type: none
          openpitrix:
            store:
              enabled: true
          persistence:
            storageClass: ''
          servicemesh:
            enabled: true
            istio:
              components:
                cni:
                  enabled: false
                ingressGateways:
                  - enabled: false
                    name: istio-ingressgateway
          terminal:
            timeout: 600
          imageRegistry:
            localRegistry: "registry.cn-beijing.aliyuncs.com"  # 添加这一行来设置本地镜像仓库地址
          13 天 后
          1 个月 后

          Cauchy ,我能不能把版本v3.3.2升级到 v3.4 过程中解决“docker hub无法使用,镜像无法拉取”这个问题,具体要怎么解决?

            参数已经生效,我在观察一下,后续镜像会不会再丢失,谢谢您@Cauchy