kk离线安装k8s报错。

Kingchan230

操作系统信息
虚拟机，Centos7.6，4C/8G

Kubernetes版本信息
v1.22.10。多节点。

KubeSphere版本信息
离线安装,全套安装。

安装kubernetes过程中，push镜像出错。

为什么推送镜像的时候，突然多了一个index-dockerhub的仓库，使用了kk创建的harbor作为registry。报错404 了，怎么解决呀，急，求指教。

chengjie

Kingchan230 正常可以push吗？

Kingchan230

chengjie 正常push镜像是可以的，但是报错的日志来看，好想是要有一个index-harbor.kubekey.local的这么一个仓库。

Kingchan230

chengjie 配置都是参考官方的，但是不知道kk在创建集群过程中，在这一步是在做什么，报错信息也看不出该如何处理。

Kingchan230

apiVersion: kubekey.kubesphere.io/v1alpha2

kind: Cluster

metadata:

name: sample

spec:

hosts:

{name: master1, address: 192.168.50.107, internalAddress: 192.168.50.107, privateKeyPath: “~/.ssh/id_rsa”}
{name: node1, address: 192.168.50.113, internalAddress: 192.168.50.113, privateKeyPath: “~/.ssh/id_rsa”}

roleGroups:

etcd:
- master1
  
  control-plane:
- master1
  
  worker:
- node1
  
  registry:
- node1
controlPlaneEndpoint:

Internal loadbalancer for apiservers

internalLoadbalancer: haproxy

domain: lb.kubesphere.local

address: ""

port: 6443

kubernetes:

version: v1.22.10

clusterName: cluster.local

autoRenewCerts: true

containerManager: docker

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
```

设置集群部署时使用的私有仓

privateRegistry: "dockerhub.kubekey.local"

namespaceOverride: "kubesphereio"

registryMirrors: []

insecureRegistries: []

addons: []

24sama

Kingchan230
可能是打的离线包有点问题，你的manifest文件是什么样的。你也可以在创建集群的命令后面加上–debug，可以打印一些更详细的日志

Kingchan230

24sama kind: Manifest

metadata:

name: sample

spec:

arches:

amd64

operatingSystems:

arch: amd64

type: linux

id: centos

version: “7”

osImage: CentOS Linux 7 (Core)

repository:

iso:

localPath: "/home/king/kubekey/centos7-rpms-amd64.iso"

url:

kubernetesDistributions:

type: kubernetes

version: v1.22.10

components:

helm:

version: v3.6.3

cni:

version: v0.9.1

etcd:

version: v3.4.13

containerRuntimes:
- type: docker
  
  version: 20.10.8
  
  crictl:
  
  version: v1.24.0
  
  docker-registry:
  
  version: “2”
  
  harbor:
  
  version: v2.4.1
  
  docker-compose:
  
  version: v2.2.2
images:
docker.io/calico/cni:v3.20.0
docker.io/calico/kube-controllers:v3.20.0
docker.io/calico/node:v3.20.0
docker.io/calico/pod2daemon-flexvol:v3.20.0
docker.io/coredns/coredns:1.8.0
docker.io/goharbor/chartmuseum-photon:v2.4.1
docker.io/goharbor/harbor-core:v2.4.1
docker.io/goharbor/harbor-db:v2.4.1
docker.io/goharbor/harbor-exporter:v2.4.1
docker.io/goharbor/harbor-jobservice:v2.4.1
docker.io/goharbor/harbor-log:v2.4.1
docker.io/goharbor/harbor-portal:v2.4.1
docker.io/goharbor/harbor-registryctl:v2.4.1
docker.io/goharbor/nginx-photon:v2.4.1
docker.io/goharbor/notary-server-photon:v2.4.1
docker.io/goharbor/notary-signer-photon:v2.4.1
docker.io/goharbor/prepare:v2.4.1
docker.io/goharbor/redis-photon:v2.4.1
docker.io/goharbor/registry-photon:v2.4.1
docker.io/goharbor/trivy-adapter-photon:v2.4.1
docker.io/kubesphere/k8s-dns-node-cache:1.15.12
docker.io/kubesphere/kube-apiserver:v1.22.1
docker.io/kubesphere/kube-apiserver:v1.22.10
docker.io/kubesphere/kube-controller-manager:v1.22.1
docker.io/kubesphere/kube-controller-manager:v1.22.10
docker.io/kubesphere/kube-proxy:v1.22.1
docker.io/kubesphere/kube-proxy:v1.22.10
docker.io/kubesphere/kube-scheduler:v1.22.1
docker.io/kubesphere/kube-scheduler:v1.22.10
docker.io/kubesphere/pause:3.4.1
docker.io/kubesphere/pause:3.5
registry.cn-beijing.aliyuncs.com/kubesphereio/cni:v3.20.0
registry.cn-beijing.aliyuncs.com/kubesphereio/coredns:1.8.0
registry.cn-beijing.aliyuncs.com/kubesphereio/k8s-dns-node-cache:1.15.12
registry.cn-beijing.aliyuncs.com/kubesphereio/kube-apiserver:v1.22.1
registry.cn-beijing.aliyuncs.com/kubesphereio/kube-apiserver:v1.22.10
registry.cn-beijing.aliyuncs.com/kubesphereio/kube-controller-manager:v1.22.1
registry.cn-beijing.aliyuncs.com/kubesphereio/kube-controller-manager:v1.22.10
registry.cn-beijing.aliyuncs.com/kubesphereio/kube-controllers:v3.20.0
registry.cn-beijing.aliyuncs.com/kubesphereio/kube-proxy:v1.22.1
registry.cn-beijing.aliyuncs.com/kubesphereio/kube-proxy:v1.22.10
registry.cn-beijing.aliyuncs.com/kubesphereio/kube-scheduler:v1.22.1
registry.cn-beijing.aliyuncs.com/kubesphereio/kube-scheduler:v1.22.10
registry.cn-beijing.aliyuncs.com/kubesphereio/node:v3.20.0
registry.cn-beijing.aliyuncs.com/kubesphereio/pause:3.5
registry.cn-beijing.aliyuncs.com/kubesphereio/pod2daemon-flexvol:v3.20.0

registry: {}

Kingchan230

24sama 麻烦再看一下呢。离线打包，根据上面的manifest最终是successful的。

Kingchan230

Kingchan230 manifest 是我通过本地，直接在线create cluster 指定1.22.10创建了一个集群，然后再用这个集群，生成这个manifest的。

Kingchan230

Kingchan230 起初以为是打的包有问题，生成了两次包，都是成功的，但是最终到部署的时候，都是404的错误。

24sama

Kingchan230
你的离线部署的环境也是amd64吗，因为我看你的离线包只打包了amd64的镜像和二进制