kubeadm

来源： https://stackoverflow.com/questions/49480707/how-to-recover-from-master-failure-with-kubeadm

来源： https://stackoverflow.com/questions/49480707/how-to-recover-from-master-failure-with-kubeadm

问题 I think my focus is on how to use this configuration parameter- "controlPlaneEndpoint". It is currently buggy to use "controlPlaneEndpoint". https://kubernetes.io/docs/setup/independent/high-availability/ I really hope you can be patient to see my actual situation. First, The configuration parameter- "controlPlaneEndpoint" is a vip or a Load balancing, right? So, I configure “controlPlaneEndpoint” with 4 layer load balancing; I tried aws\ali. All the results show that will be probability of

问题 I set up a k8s cluster using kubeadm (v1.18) on an Ubuntu virtual machine. Now I need to add an Ingress Controller. I decided for nginx (but I'm open for other solutions). I installed it according to the docs, section "bare-metal": kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-0.31.1/deploy/static/provider/baremetal/deploy.yaml The installation seems fine to me: kubectl get all -n ingress-nginx NAME READY STATUS RESTARTS AGE pod/ingress-nginx-admission

问题 I want to enable the Kube-proxy mode to IPVS in the existing cluster. currently, it is running on IPtables. how can I change it to IPVS without affecting the existing workload? I have already installed all the required modules to enable it. Also, my cluster is installed using kubeadm but, I have not used the configuration file during installation. what should be the command exactly to enable the IPVS on my cluster. documentation1 documentation2 回答1: Edit the configmap kubectl edit configmap

问题 I'm using k8s with kubeadm version 1.17. I'm trying to enable Service Topology feature gates but I can't. Documentation say to use "--feature-gates="ServiceTopology=true,EndpointSlice=true". I tried to use that in "kubeadm init"... But kubeadm say that is not available to the cluster. Can you help me? That is the documentation that I'm following: https://kubernetes.io/docs/tasks/administer-cluster/enabling-service-topology/ 回答1: It's not a flag of kubeadm. You need to enable it for each

问题 I'm trying to limit the number of pods per each node from my cluster. I managed to add a global limit per node from kubeadm init with config file: apiVersion: kubeadm.k8s.io/v1beta1 kind: ClusterConfiguration networking: podSubnet: <subnet> --- apiVersion: kubelet.config.k8s.io/v1beta1 kind: KubeletConfiguration maxPods: 10 This is not quite well because the limit is applied even on master node (where multiple kube-system pods are running and the number of pods here may increase over 10). I

问题 When I reboot the master and work node, the pod of coredns show the below error message seem that it can not recreate kubelet after server restart. Normal SandboxChanged 12s kubelet, izbp1dyjigsfwmw0dtl85gz Pod sandbox changed, it will be killed and re-created. Warning FailedCreatePodSandBox 11s kubelet, izbp1dyjigsfwmw0dtl85gz Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "5e850ee3e8bf86688fec2badd9b0272127a0d775620a5783e7c30b4e0d412b01"

问题 When I reboot the master and work node, the pod of coredns show the below error message seem that it can not recreate kubelet after server restart. Normal SandboxChanged 12s kubelet, izbp1dyjigsfwmw0dtl85gz Pod sandbox changed, it will be killed and re-created. Warning FailedCreatePodSandBox 11s kubelet, izbp1dyjigsfwmw0dtl85gz Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "5e850ee3e8bf86688fec2badd9b0272127a0d775620a5783e7c30b4e0d412b01"

问题 When I reboot the master and work node, the pod of coredns show the below error message seem that it can not recreate kubelet after server restart. Normal SandboxChanged 12s kubelet, izbp1dyjigsfwmw0dtl85gz Pod sandbox changed, it will be killed and re-created. Warning FailedCreatePodSandBox 11s kubelet, izbp1dyjigsfwmw0dtl85gz Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "5e850ee3e8bf86688fec2badd9b0272127a0d775620a5783e7c30b4e0d412b01"