What are the problems of kubenertes 1.16 cluster deployment?
This article is to share with you about kubenertes 1.16 cluster deployment problems, the editor feels very practical, so share with you to learn, I hope you can learn something after reading this article, say no more, follow the editor to have a look.
Installation uses CentOS7.5 installed under virtual box, and Ansible one-click installation script under Easypack is used to install kubernetes1.16, dashbaord and coredns. Two problems are encountered in the process, which are sorted out as follows.
Version changes:
Only the Kubernetes version has been changed
Component update previous version current version
Kubernetes 1.15.0 1.16.0
Docker 18.09.7 18.09.7
ETCD 3.3.13 3.3.13
FLANNEL 0.10.0 0.11.0
Problem 1:coredns installation failed
Reason:
The apiVersion of Deployment in coredns.yml is discarded as extensions/v1beta1,extensions/v1beta1, which results in an execution error.
An example of a core.yml file is as follows
[root@host132 ansible] # cat / etc/k8s/coredns/coredns.yaml # _ _ MACHINE_GENERATED_WARNING__... Omit-apiVersion: extensions/v1beta1kind: Deploymentmetadata: name: coredns namespace: kube-system labels: k8s-app: kube-dns kubernetes.io/cluster-service: "true" addonmanager.kubernetes.io/mode: Reconcile kubernetes.io/name: "CoreDNS". Omit [root@host132 ansible] #
Corresponding method:
Just change it to apps/v1.
[root@host132 templates] # git diff coredns.yaml diff-- git a/k8s/ansible/coredns/templates/coredns.yaml b/k8s/ansible/coredns/templates/coredns.yamlindex 96abe75..69af15a 100644FUFUR-- loadbalance K8s apiVersion: extensions/v1beta1+apiVersion: apps/v1 kind: Deployment metadata: name: coredns [root@host132 templates] #
Question 2: kubectl get cs is displayed as unknown
Examples of error messages are as follows:
[root@host132 ansible] # kubectl get csNAME AGEschedulercontroller-manageretcd-0 [root@host132 ansible] #
There does not seem to be much impact, there is no corresponding for the time being, and the subsequent reasons will continue to be updated after confirmation.
The above are the problems of kubenertes 1.16 cluster deployment, and the editor believes that there are some knowledge points that we may see or use in our daily work. I hope you can learn more from this article. For more details, please follow the industry information channel.
