невозможно распознать "kube-flannel.yml": нет совпадений для вида "DaemonSet" в версии "extensions / v1beta1" - PullRequest
Новая
       39

невозможно распознать "kube-flannel.yml": нет совпадений для вида "DaemonSet" в версии "extensions / v1beta1"

1 голос
/ 21 ноября 2019

Я использую мастер K8s (Ubuntu 16.04) и узел (Ubuntu 16.04) на Vm Hyper-V, и не могу присоединиться к узлу, ни готовые модули coredns.

На рабочем узле k8s:

admin1 @ POC-k8s-node1: ~ $ sudo kubeadm join 192.168.137.2:6443 --token s03usq.lrz343lolmrz00lf --discovery-token-ca-cert-hash sha256: 5c6b88a78e7b303debda447fa6f7fb48e3746bedc07dc2a518fbc80d48f37ba4 --ignore-preflight-errors = все 

[preflight] Running pre-flight checks
        [WARNING IsDockerSystemdCheck]: detected "cgroupfs" as the Docker cgroup driver. The recommended driver is "systemd". Please follow the guide at https://kubernetes.io/docs/setup/cri/
        [WARNING SystemVerification]: this Docker version is not on the list of validated versions: 19.03.5. Latest validated version: 18.09
        [WARNING Port-10250]: Port 10250 is in use
[preflight] Reading configuration from the cluster...
[preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -oyaml'
[kubelet-start] Downloading configuration for the kubelet from the "kubelet-config-1.16" ConfigMap in the kube-system namespace
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Activating the kubelet service
[kubelet-start] Waiting for the kubelet to perform the TLS Bootstrap...
[kubelet-check] Initial timeout of 40s passed.
error execution phase kubelet-start: error uploading crisocket: timed out waiting for the condition
To see the stack trace of this error execute with --v=5 or higher

admin1 @ POC-k8s * узел1: ~ $ journalctl * * 100 * 100 * k * 100 * 100 * k * 100 * 100 * k * 100 * 100 * k * 100 * 100 * k * 100 * 100 * k * * * 100 * * * * * * * * * * * * * * * * * * * * * 100 * 100 * 100 * 100 * 100 * 100 * 100 * 100 * k * * * 100 * * * * * * * * * * * * * * * * 100 * 100 * 100 * 100 * 100 * 100 * 100 * 100 * k * * * * * * * * * * * * * * 100 * 100 * 100 * 100 * 100 * 100 * 100 * k * * * * * * * *POC-k8s-node1: / home / admin1 # journalctl -xe -f 

Nov 21 06:30:45 POC-k8s-node1 kubelet[75467]: E1121 06:30:45.670520   75467 reflector.go:123] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:46: Failed to list *v1.Pod: Unauthorized
Nov 21 06:30:45 POC-k8s-node1 kubelet[75467]: E1121 06:30:45.691050   75467 kubelet.go:2267] node "poc-k8s-node1" not found
Nov 21 06:30:45 POC-k8s-node1 kubelet[75467]: E1121 06:30:45.791249   75467 kubelet.go:2267] node "poc-k8s-node1" not found
Nov 21 06:30:45 POC-k8s-node1 kubelet[75467]: E1121 06:30:45.866004

На K8s Master: root @ POC-k8s-master: ~ # образы конфигурации kubeadm pull 

[config/images] Pulled k8s.gcr.io/kube-apiserver:v1.16.3
[config/images] Pulled k8s.gcr.io/kube-controller-manager:v1.16.3
[config/images] Pulled k8s.gcr.io/kube-scheduler:v1.16.3
[config/images] Pulled k8s.gcr.io/kube-proxy:v1.16.3
[config/images] Pulled k8s.gcr.io/pause:3.1
[config/images] Pulled k8s.gcr.io/etcd:3.3.15-0
[config/images] Pulled k8s.gcr.io/coredns:1.6.2
root@POC-k8s-master:~# export KUBECONFIG=/etc/kubernetes/admin.conf

root @ POC-k8s-master: ~ # sysctl net.bridge.bridge-nf-call-iptables = 1 

net.bridge.bridge-nf-call-iptables = 1

root @ POC-k8s-master: ~ # kubectl getpods --all-namespaces 

NAMESPACE     NAME                                     READY   STATUS    RESTARTS   AGE
*****kube-system   coredns-5644d7b6d9-7xk42                 0/1     Pending   0          91s
kube-system   coredns-5644d7b6d9-mbrlx                 0/1     Pending   0          91s*****
kube-system   etcd-poc-k8s-master                      1/1     Running   0          51s
kube-system   kube-apiserver-poc-k8s-master            1/1     Running   0          32s
kube-system   kube-controller-manager-poc-k8s-master   1/1     Running   0          47s
kube-system   kube-proxy-xqb2d                         1/1     Running   0          91s
kube-system   kube-scheduler-poc-k8s-master            1/1     Running   0          38s

root @ POC-k8s-master: ~ # kubectl apply -f 

https://raw.githubusercontent.com/coreos/flannel/c5d10c8/Documentation/kube-flannel.yml
clusterrole.rbac.authorization.k8s.io/flannel created
clusterrolebinding.rbac.authorization.k8s.io/flannel created
serviceaccount/flannel created
configmap/kube-flannel-cfg created
unable to recognize "https://raw.githubusercontent.com/coreos/flannel/c5d10c8/Documentation/kube-flannel.yml": no matches for kind "DaemonSet" in version "extensions/v1beta1"
unable to recognize "https://raw.githubusercontent.com/coreos/flannel/c5d10c8/Documentation/kube-flannel.yml": no matches for kind "DaemonSet" in version "extensions/v1beta1"
unable to recognize "https://raw.githubusercontent.com/coreos/flannel/c5d10c8/Documentation/kube-flannel.yml": no matches for kind "DaemonSet" in version "extensions/v1beta1"
unable to recognize "https://raw.githubusercontent.com/coreos/flannel/c5d10c8/Documentation/kube-flannel.yml": no matches for kind "DaemonSet" in version "extensions/v1beta1"
unable to recognize "https://raw.githubusercontent.com/coreos/flannel/c5d10c8/Documentation/kube-flannel.yml": no matches for kind "DaemonSet" in version "extensions/v1beta1"

Ответы [ 2 ]

2 голосов
/ 21 ноября 2019

Кажется, вы используете k8s версии 1.16 и измените группу API daemonset на apps/v1

Обновите ссылку на это: https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml

А также существует проблема по этому поводутам: https://github.com/kubernetes/website/issues/16441

1 голос
/ 21 ноября 2019

Первая часть вопроса решена с помощью «#kubeadm reset» на узле, а затем сработала команда присоединения! Поскольку 2-я часть вопроса была решена первой, следовательно, вопрос можно было решить, поэтому @Alireza David большое спасибо.

...