ARM加上一台X86的服务器来部署harbor，kk不能把arm的镜像包推上harbor里去吗

[GalenGao]

Your current KubeKey version

3.1.9

Describe this feature

因为kk不支持arm的habor，所以规划其中一台x86的来部署harbor，但是推送镜像的时候总是推送不上去。

Describe the solution you'd like

我们试过下载arm 和amd的混合离线包也有问题，纯arm的离线包也有问题

Additional information

No response

[skyhhjmk]

配置文件config-sample.yaml

apiVersion: kubekey.kubesphere.io/v1alpha2 kind: Cluster metadata: name: sample spec: hosts:

• {name: host, address: 20.48.5.133, internalAddress: 20.48.5.133, user: root, password: "xxxxx",arch: arm64}

建议使用代码块以保留缩进并且方便阅读，使用方法：

```yaml

在里面粘贴你的配置文件

```

[GalenGao]

apiVersion: kubekey.kubesphere.io/v1alpha2
kind: Cluster
metadata:
  name: sample
spec:
  hosts:
  - {name: host, address: 20.48.5.133, internalAddress: 20.48.5.133, user: root, password: "xxxxx",arch: arm64}
  - {name: member1, address: 20.48.1.130, internalAddress: 20.48.1.130, user: root, password: "xxxxx",arch: arm64}
  - {name: member2, address: 20.48.1.68, internalAddress: 20.48.1.68, user: root, password: "xxxxx",arch: amd}
  roleGroups:
    etcd:
    - host
    control-plane: 
    - host
    worker:
    - member1
    registry:
    - member2
  controlPlaneEndpoint:
    ## Internal loadbalancer for apiservers 
    # internalLoadbalancer: haproxy

    domain: lb.kubesphere.local
    address: ""
    port: 6443
  kubernetes:
    version: v1.33.0
    clusterName: cluster.local
    autoRenewCerts: true
    containerManager: containerd
  etcd:
    type: kubekey
  network:
    plugin: calico
    kubePodsCIDR: 10.233.64.0/18
    kubeServiceCIDR: 10.233.0.0/18
    ## multus support. https://github.com/k8snetworkplumbingwg/multus-cni
    multusCNI:
      enabled: false
  registry:
    type: harbor
    auths:
      "dockerhub.kubekey.local":
        username: admin
        password: Harbor12345
        skipTLSVerify: false
        plainHTTP: false # Allow contacting registries over HTTP.
        certsPath: "/etc/docker/certs.d/dockerhub.kubekey.local" # Use certificates at path (*.crt, *.cert, *.key) to connect to the registry.
    privateRegistry: "dockerhub.kubekey.local"
    namespaceOverride: "kubesphereio"
    registryMirrors: []
    insecureRegistries: []
    containerdDataDir: /data/containerd
    dockerDataDir: /data/docker
    registryDataDir: /data/harbor/registry
  addons: []

[junlintianxiazhifulinzhongguo]

现在 kubekey 支持 k8s 集群节点同时有 不同的cpu 架构吗，我看上面都有 amd 和 arm ，支持下面这种吗： hosts:

• {name: master1, address: 20.48.5.133, internalAddress: 20.48.5.131, user: root, password: "xxxxx",arch: arm64}
• {name: master2, address: 20.48.5.133, internalAddress: 20.48.5.132, user: root, password: "xxxxx",arch: amd}
• {name: master3, address: 20.48.5.133, internalAddress: 20.48.5.133, user: root, password: "xxxxx",arch: arm64}
• {name: work1, address: 20.48.1.68, internalAddress: 20.48.1.61, user: root, password: "xxxxx",arch: amd}
• {name: work2, address: 20.48.1.68, internalAddress: 20.48.1.62, user: root, password: "xxxxx",arch: arm64} roleGroups: etcd:
  • master1
  • master2
  • master3 control-plane:
• master1 - master2 - master3 worker: - work1 - work2

[pixiake]

Your current KubeKey version

3.1.9

Describe this feature

因为kk不支持arm的habor，所以规划其中一台x86的来部署harbor，但是推送镜像的时候总是推送不上去。

Describe the solution you'd like

我们试过下载arm 和amd的混合离线包也有问题，纯arm的离线包也有问题

Additional information

No response

authentication required If the login information of harbor is configured in the configuration file, it is also necessary to ensure that the images' projects has been created in harbor before pushing the image. For example, kubesphereio in the screenshot.

[pixiake]

现在 kubekey 支持 k8s 集群节点同时有 不同的cpu 架构吗，我看上面都有 amd 和 arm ，支持下面这种吗： hosts:

• {name: master1, address: 20.48.5.133, internalAddress: 20.48.5.131, user: root, password: "xxxxx",arch: arm64}

• {name: master2, address: 20.48.5.133, internalAddress: 20.48.5.132, user: root, password: "xxxxx",arch: amd}

• {name: master3, address: 20.48.5.133, internalAddress: 20.48.5.133, user: root, password: "xxxxx",arch: arm64}

• {name: work1, address: 20.48.1.68, internalAddress: 20.48.1.61, user: root, password: "xxxxx",arch: amd}

• {name: work2, address: 20.48.1.68, internalAddress: 20.48.1.62, user: root, password: "xxxxx",arch: arm64} roleGroups: etcd:

  • master1
  • master2
  • master3 control-plane:

• master1

  • master2
  • master3 worker:
  • work1
  • work2

Support hybrid architectures: amd64 and arm64 （default is amd64）