Styjun

Is the book wrong about the Nyquist Sampling Criterion?

Is there precedent or are there procedures for a US president refusing to concede to an electoral defeat?

Clean sphere separation with a sphere created from a cube

Copy previous line to current line from text file

Undefined Control Sequence for my 0-norm

The origin of list data structure

What Kind of Wooden Beam is this

What was the first story to feature the plot "the monsters were human all along"?

My first C++ game (snake console game)

How can I get people to remember my character's gender?

How to preserve a rare version of a book?

Piano: quaver triplets in RH v dotted quaver and semiquaver in LH

What does にとり mean？

Understanding ties

GitLab account hacked and repo wiped

How do I allocate more memory to an app on Sheepshaver running Mac OS 9?

How to remove carriage bolts from a basketball backboard?

Motion-trail-like lines

In linear regression why does regularisation penalise the parameter values as well?

How to properly store the current value of int variable into a token list?

Is there a word for food that's gone 'bad', but is still edible?

Should I simplify my writing in a foreign country?

Is there a word that describes the unjustified use of a more complex word?

Hostile Divisor Numbers

etcd 3rd pod not getting scheduled on master node due to peers expecting old cert

kubernetes + coreos cluster - replacing certificateskube-dns and kubernetes-dashboard pods status are CrashLoopBackOffkube-apiserver unable to communicate with TLS enabled etcdkubectl commands timeout without detailsScheduler is not scheduling Pod for DaemonSet in Master nodeConsul DNS and KubernetesnodeAffinity with preferredDuringSchedulingIgnoredDuringExecution set always schedules a pod on an incorrect nodeDisaster Recovery Kops Kubernetes Master Node on AWSstoring the configuration used in ConfigMap “kubeadm-config” in the “kube-system” NamespaceKubernetes cert-manager not updating certificates after issuer change

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;

0

needed hint to resolve etcd cert issue on two etcd server pods

I have 2(3) etcd server pods and these are reporting for 3rd pod that x.509 cert is valid for etc.test1.com and not for etc.test2.com

so, my assumption is, issue is etcd server pod 2 & 3 are somehow expecting old cert dns name and not new cert dns name value which is etc.test2.com>

this is causing the 3rd pod to never get accepted as a valid peer and pod never gets scheduled on node.

Any hint how can I reset the two PODS that are expecting old cert and start expecting new cert?

below is the error from etcd server pods that are running .

rafthttp: health check for peer 44ffe8e24fa23c10 could not connect: x509: certificate is valid for etcd-a.internal.test1.com, etcd-b.internal.test1.com, etcd-c.internal.test1.com, etcd-events-a.internal.test1.com, etcd-events-b.internal.test1.com, etcd-events-c.internal.test1.com, localhost, not etcd-b.internal.test2.com

Also, will cluster work on single etcd server pod or does it need to have 3?

kubernetes etcd3

share|improve this question

edited Mar 23 at 3:52

fma abd

asked Mar 23 at 2:56

fma abdfma abd

327

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  You have created the cluster manually or you are running under a ready cluster provided by the cloud provider ?
  
  – Investigator
  Mar 23 at 23:17
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Connect to one controller node and issue the following command: sudo ETCDCTL_API=3 etcdctl member list --endpoints=127.0.0.1:2379 --cacert=/etc/etcd/ca.pem --cert=/etc/etcd/kubernetes.pem --key=/etc/etcd/kubernetes-key.pem
  
  – Investigator
  Mar 23 at 23:19
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I created it using kops tool and issue was that DNS records were somehow wrongly updated to wrong IP addresses. So, i switched them to right ones and then ETCDs starting talking to right peers and no TLS cert issue was observed. I also had to start the etcd pod using docker run. so this solved my issue. we can close question.
  
  – fma abd
  Apr 16 at 16:20
  

  
  
  
  

add a comment | 

0

needed hint to resolve etcd cert issue on two etcd server pods

I have 2(3) etcd server pods and these are reporting for 3rd pod that x.509 cert is valid for etc.test1.com and not for etc.test2.com

so, my assumption is, issue is etcd server pod 2 & 3 are somehow expecting old cert dns name and not new cert dns name value which is etc.test2.com>

this is causing the 3rd pod to never get accepted as a valid peer and pod never gets scheduled on node.

Any hint how can I reset the two PODS that are expecting old cert and start expecting new cert?

below is the error from etcd server pods that are running .

rafthttp: health check for peer 44ffe8e24fa23c10 could not connect: x509: certificate is valid for etcd-a.internal.test1.com, etcd-b.internal.test1.com, etcd-c.internal.test1.com, etcd-events-a.internal.test1.com, etcd-events-b.internal.test1.com, etcd-events-c.internal.test1.com, localhost, not etcd-b.internal.test2.com

Also, will cluster work on single etcd server pod or does it need to have 3?

kubernetes etcd3

share|improve this question

edited Mar 23 at 3:52

fma abd

asked Mar 23 at 2:56

fma abdfma abd

327

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  You have created the cluster manually or you are running under a ready cluster provided by the cloud provider ?
  
  – Investigator
  Mar 23 at 23:17
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Connect to one controller node and issue the following command: sudo ETCDCTL_API=3 etcdctl member list --endpoints=127.0.0.1:2379 --cacert=/etc/etcd/ca.pem --cert=/etc/etcd/kubernetes.pem --key=/etc/etcd/kubernetes-key.pem
  
  – Investigator
  Mar 23 at 23:19
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I created it using kops tool and issue was that DNS records were somehow wrongly updated to wrong IP addresses. So, i switched them to right ones and then ETCDs starting talking to right peers and no TLS cert issue was observed. I also had to start the etcd pod using docker run. so this solved my issue. we can close question.
  
  – fma abd
  Apr 16 at 16:20
  

  
  
  
  

add a comment | 

needed hint to resolve etcd cert issue on two etcd server pods

I have 2(3) etcd server pods and these are reporting for 3rd pod that x.509 cert is valid for etc.test1.com and not for etc.test2.com

so, my assumption is, issue is etcd server pod 2 & 3 are somehow expecting old cert dns name and not new cert dns name value which is etc.test2.com>

this is causing the 3rd pod to never get accepted as a valid peer and pod never gets scheduled on node.

Any hint how can I reset the two PODS that are expecting old cert and start expecting new cert?

below is the error from etcd server pods that are running .

rafthttp: health check for peer 44ffe8e24fa23c10 could not connect: x509: certificate is valid for etcd-a.internal.test1.com, etcd-b.internal.test1.com, etcd-c.internal.test1.com, etcd-events-a.internal.test1.com, etcd-events-b.internal.test1.com, etcd-events-c.internal.test1.com, localhost, not etcd-b.internal.test2.com

Also, will cluster work on single etcd server pod or does it need to have 3?

kubernetes etcd3

share|improve this question

edited Mar 23 at 3:52

fma abd

asked Mar 23 at 2:56

fma abdfma abd

327

rafthttp: health check for peer 44ffe8e24fa23c10 could not connect: x509: certificate is valid for etcd-a.internal.test1.com, etcd-b.internal.test1.com, etcd-c.internal.test1.com, etcd-events-a.internal.test1.com, etcd-events-b.internal.test1.com, etcd-events-c.internal.test1.com, localhost, not etcd-b.internal.test2.com

kubernetes etcd3

kubernetes etcd3

share|improve this question

edited Mar 23 at 3:52

fma abd

asked Mar 23 at 2:56

fma abdfma abd

327

share|improve this question

edited Mar 23 at 3:52

fma abd

asked Mar 23 at 2:56

fma abdfma abd

327

asked Mar 23 at 2:56

fma abdfma abd

327

asked Mar 23 at 2:56

fma abdfma abd

327