kubernetes-health-check

问题 Deploying an ignite cluster within Kubernetes, I cam across an issue that prevents cluster members from joining the group. If I use a readinessProbe and a livenessProbe, even with a delay as low as 10 seconds, they nodes never join each other. If I remove those probes, they find each other just fine. So, my question is: can you use these probes to monitor node health, and if so, what are appropriate settings. On top of that, what would be good, fast health checks for Ignite, anyway? 回答1:

问题 Deploying an ignite cluster within Kubernetes, I cam across an issue that prevents cluster members from joining the group. If I use a readinessProbe and a livenessProbe, even with a delay as low as 10 seconds, they nodes never join each other. If I remove those probes, they find each other just fine. So, my question is: can you use these probes to monitor node health, and if so, what are appropriate settings. On top of that, what would be good, fast health checks for Ignite, anyway? 回答1:

问题 Deploying an ignite cluster within Kubernetes, I cam across an issue that prevents cluster members from joining the group. If I use a readinessProbe and a livenessProbe, even with a delay as low as 10 seconds, they nodes never join each other. If I remove those probes, they find each other just fine. So, my question is: can you use these probes to monitor node health, and if so, what are appropriate settings. On top of that, what would be good, fast health checks for Ignite, anyway? 回答1:

问题 I am using the following code in statefulset.yml apiVersion: apps/v1 kind: StatefulSet metadata: name: geth namespace: prod spec: serviceName: geth-service replicas: 2 selector: matchLabels: app: geth-node template: metadata: labels: app: geth-node spec: containers: - name: geth-node image: <My image> imagePullPolicy: Always livenessProbe: httpGet: path: / port: 8545 initialDelaySeconds: 20 #wait this period after staring fist time periodSeconds: 15 # polling interval timeoutSeconds: 5 # wish

问题 Can I add some config so that my daemon pods start before other pods can be scheduled or nodes are designated as ready? Adding post edit: These are 2 different pods altogether, the daemonset is a downstream dependency to any pods that might get scheduled on the host. 回答1: There's no such a thing as Pod hierarchy in Kubernetes between multiple separate types of pods. Meaning belonging to different Deployments, Statefulsets, Daemonsets, etc. In other words, there is no notion of a master pod

问题 I am currently using Deployments to manage my pods in my K8S cluster. Some of my deployments require 2 pods/replicas, some require 3 pods/replicas and some of them require just 1 pod/replica. The issue Im having is the one with one pod/replica. My YAML file is : apiVersion: extensions/v1beta1 kind: Deployment metadata: name: user-management-backend-deployment spec: replicas: 1 strategy: type: RollingUpdate rollingUpdate: maxUnavailable: 1 maxSurge: 2 selector: matchLabels: name: user

来源： https://stackoverflow.com/questions/44012694/how-fix-this-error-watch-chan-error-etcdserver-mvcc-required-revision-has-be

问题 Having a kubernetes service (of type ClusterIP ) connected to a set of pod s, but none of them are currently ready - what will happen to the request? Will it: fail eagerly timeout wait until a ready pod is available (or forever, whichever is earlier) something else? 回答1: It will time out. Kube-proxy pulls out the IP addresses from healthy pods and sets as endpoints of the service (backends). Also, note that all kube-proxy does is to re-write the iptables when you create, delete or modify a

问题 Having a kubernetes service (of type ClusterIP ) connected to a set of pod s, but none of them are currently ready - what will happen to the request? Will it: fail eagerly timeout wait until a ready pod is available (or forever, whichever is earlier) something else? 回答1: It will time out. Kube-proxy pulls out the IP addresses from healthy pods and sets as endpoints of the service (backends). Also, note that all kube-proxy does is to re-write the iptables when you create, delete or modify a

问题 I have set up the nginx ingress controller following this guide. The ingress works well and I am able to visit the defaultbackend service and my own service as well. But when reviewing the objects created in the Google Cloud Console, in particular the load balancer object which was created automatically, I noticed that the health check for the other nodes are failing: Is this because the ingress controller process is only running on the one node, and so it's the only one that passes the