kubeadm

问题 I am trying to setup a single-node cluster on my single board computer (non raspberry), running armbian (ubuntu bionic based kernel 4.19). I set up everything according to the official guides, but when I try to run kubeadm init it fails with timed out waiting for the condition when it's starting the control plane. I read all the issues and questions about this problem, but nothing seems to be working for me. I also tried different kubernetes versions, but got the same results. Here are all my

问题 How can I confirm whether or not some of the pods in this Kubernetes cluster are running inside the Calico overlay network? Pod Names: Specifically, when I run kubectl get pods --all-namespaces , only two of the nodes in the resulting list have the word calico in their names. The other pods, like etcd and kube-controller-manager , and others do NOT have the word calico in their names. From what I read online, the other pods should have the word calico in their names. $ kubectl get pods --all

问题 I am following with the answer here step 6th. To make my own local minikube cluster of single master and 2 nodes . master names minikube . $ kubeadm version kubeadm version: &version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.3", GitCommit:"721bfa751924da8d1680787490c54b9179b1fed0", GitTreeState:"clean", BuildDate:"2019-02-01T20:05:53Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"} $ kubelet --version Kubernetes v1.13.3 login to the minikube console by minikube ssh Then

问题 I have set up a custom kubernetes cluster on GCE using kubeadm. I am trying to use StatefulSets with persistent storage. I have the following configuration: kind: StorageClass apiVersion: storage.k8s.io/v1 metadata: name: gce-slow provisioner: kubernetes.io/gce-pd parameters: type: pd-standard zones: europe-west3-b --- apiVersion: apps/v1 kind: StatefulSet metadata: name: myname labels: app: myapp spec: serviceName: myservice replicas: 1 selector: matchLabels: app: myapp template: metadata:

问题 I install kubernetes v1.11.5 from kubeadm with cni plugin flannel and everything is ok. But I after try to switch to calico I found that the cross machine pod communication is broken. So I switch back to flannel. But got error message when creating pod: It seems that I need to reset cni network? But I don't know how to solve this problem. My flannel and calico installation is follow kubeadm instruction with zero config update. 回答1: I use following steps to remove old calico configs from

问题 Question Which format of kubeadm init --token is correct? (2/4) Initializing your master shows "--token xyz". kubeadm join --token <token> <master-ip>:<master-port> --discovery-token-ca-cert-hash sha256:<hash> kubeadm init shows "--token=xyz". kubeadm join --token=abcdef.1234567890abcdef --discovery-token-ca-cert-hash sha256:1234..cdef 192.168.1.1:6443 The execution log (using Ansible) showed several error message. Wonder if this is related with the format. changed: [192.168.99.12] => {... "

问题 So I know how to add a worker node to an existing Kubernetes 1.14 cluster (that was set up with kubeadm ): kubeadm token create --print-join-command will print a valid kubeadm join command with correct values for arguments --token and --discovery-token-ca-cert-hash . I currently understand that for adding another node to the control plane (master node) kubeadm join requires the additional arguments --experimental-control-plane (w/o value) and --certificate-key . This is for stacked control

问题 I need that tomcat is registered with my Node IP and a port. My question is: At the moment that i run the command: kubectl run tomcat-pod --image=tomcat --port=80 --labels="name=tomcat-pod" In this moment the tomcat is running. Then I believe that exposing like a service my tomcat with NodePort type, It will change my IP registration, because i have understanded that my server is registered with the command run? Or what is the correct way to register my app with the Node machine using the

问题 I'm a bit confused by this, because it was working for days without issue. I use to be able to join nodes to my cluster withoout issue. I would run the below on the master node: kubeadm init ..... After that, it would generate a join command and token to issue to the other nodes I want to join. Something like this: kubeadm join --token 99385f.7b6e7e515416a041 192.168.122.100 I would run this on the nodes, and they would join without issue. The next morning, all of a sudden this stopped

问题 I'm trying to follow this tutorial. What would be the advantage of generating the certs yourself instead of depending on kubeadm? if you create the certs yourself, does the auto-rotation happens after setting up the cluster from kubeadm? Thanks! 回答1: No major advantage. kubeadm does the same: generate self-signed certs. The only mini advantage is that you could add some custom values in the CSR, such as a City, Organization, etc. Not really. There's a kubelet certificate rotation flag -