kubeadm

问题 I'm running kubeadm init --pod-network-cidr=10.244.0.0/16 to deploy k8s. After it i'm running kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/2140ac876ef134e0ed5af15c65e414cf26827915/Documentation/kube-flannel.yml to install Flannel pod network. Right after it i have core dns pods up and runnig, but logs say: [INFO] plugin/reload: Running configuration MD5 = 4e235fcc3696966e76816bcd9034ebc7 CoreDNS-1.6.5 linux/amd64, go1.13.4, c2fd1b2 [ERROR] plugin/errors: 2

问题 How to install kubeadm for Kubernetes in macOS. When tempting to use brew install kubeadm I get this error Error: No available formula with the name "kubeadm" ==> Searching for a previously deleted formula (in the last month).. NB : In macOS I can't use apt-get 回答1: Not sure about MAC OS The supported platforms on their list are: Ubuntu 16.04+ Debian 9 CentOS 7 RHEL 7 Fedora 25/26 (best-effort) HypriotOS v1.0.1+ Container Linux (tested with 1800.6.0) https://kubernetes.io/docs/setup

问题 How to install kubeadm for Kubernetes in macOS. When tempting to use brew install kubeadm I get this error Error: No available formula with the name "kubeadm" ==> Searching for a previously deleted formula (in the last month).. NB : In macOS I can't use apt-get 回答1: Not sure about MAC OS The supported platforms on their list are: Ubuntu 16.04+ Debian 9 CentOS 7 RHEL 7 Fedora 25/26 (best-effort) HypriotOS v1.0.1+ Container Linux (tested with 1800.6.0) https://kubernetes.io/docs/setup

问题 I setup my cluster by kubeadm. At the last step i exec kubeadm init --config kubeadm.conf --v=5 . I get the error about the clusterIp value. Here is the part of the output: I0220 00:16:27.625920 31630 clusterinfo.go:79] creating the RBAC rules for exposing the cluster-info ConfigMap in the kube-public namespace I0220 00:16:27.947941 31630 kubeletfinalize.go:88] [kubelet-finalize] Assuming that kubelet client certificate rotation is enabled: found "/var/lib/kubelet/pki/kubelet-client-current

问题 I setup my cluster by kubeadm. At the last step i exec kubeadm init --config kubeadm.conf --v=5 . I get the error about the clusterIp value. Here is the part of the output: I0220 00:16:27.625920 31630 clusterinfo.go:79] creating the RBAC rules for exposing the cluster-info ConfigMap in the kube-public namespace I0220 00:16:27.947941 31630 kubeletfinalize.go:88] [kubelet-finalize] Assuming that kubelet client certificate rotation is enabled: found "/var/lib/kubelet/pki/kubelet-client-current

问题 Context I installed Docker following this instruction on my Ubuntu 18.04 LTS (Server) and later on Kubernetes followed via kubeadm . After initializing ( kubeadm init --pod-network-cidr=10.10.10.10/24 ) and joining a second node (I got a two node cluster for the start) I cannot get my coredns as well as the later applied Web UI (Dashboard) to actually go into status Running . As pod network I tried both, Flannel ( kubectl apply -f https://raw.githubusercontent.com/coreos/flannel

问题 Issue Redis POD creation on k8s(v1.10) cluster and POD creation stuck at "ContainerCreating" Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 30m default-scheduler Successfully assigned redis to k8snode02 Normal SuccessfulMountVolume 30m kubelet, k8snode02 MountVolume.SetUp succeeded for volume "default-token-f8tcg" Warning FailedCreatePodSandBox 5m (x1202 over 30m) kubelet, k8snode02 Failed create pod sandbox: rpc error: code = Unknown desc = NetworkPlugin cni

问题 Use kubeadm to install Kubernetes cluster by Vagrant followed official guide: https://kubernetes.io/docs/getting-started-guides/kubeadm/ It was successful when install on master host: kubeadm init And generated a token: [root@localhost ~]# kubeadm token list TOKEN TTL EXPIRES USAGES DESCRIPTION 1eb2c2.8c9s81b32cc9937e <forever> <never> authentication,signing The default bootstrap token generated by 'kubeadm init'. Use this token to join from nodes hosts: kubeadm join --token=1eb2c2

问题 I created a kubernetes cluster 1 master and 2 worker nodes 2 months ago, today one worker node started to fail and I don't know why. I think nothing unusual happened to my worker. I used flannel and kubeadm to create the cluster and it was working very well. If I describe the node: tommy@bxybackend:~$ kubectl describe node bxybackend-node01 Name: bxybackend-node01 Roles: <none> Labels: beta.kubernetes.io/arch=amd64 beta.kubernetes.io/os=linux kubernetes.io/arch=amd64 kubernetes.io/hostname

问题 Configuration for cgroup driver is right in /etc/systemd/system/kubelet.service.d/10-kubeadm.conf Environment="KUBELET_CGROUP_ARGS=--cgroup-driver=systemd" I also checked the Environment with cli $ systemctl show --property=Environment kubelet | cat Environment=KUBELET_KUBECONFIG_ARGS=--kubeconfig=/etc/kubernetes/kubelet.conf\x20--require-kubeconfig=true KUBELET_SYSTEM_PODS_ARGS=--pod-manifest-path=/etc/kubernetes/manifests\x20--allow-privileged=true KUBELET_NETWORK_ARGS=--network-plugin=cni