Matteo Olivi
Matteo Olivi
The etcd cluster members used static TLS: ``` apiVersion: etcd.database.coreos.com/v1beta2 kind: EtcdCluster metadata: name: the-etcd-cluster namespace: example-com spec: size: 3 version: "3.3.11" TLS: static: member: peerSecret: etcd-peer serverSecret: etcd-server operatorSecret:...
As an addition: after the second member of the etcd cluster got stuck in failed state, the etcd operator logs contained: > time="2020-02-11T13:57:33Z" level=info msg="Start reconciling" cluster-name=the-etcd-cluster cluster-namespace=example-com pkg=cluster >...
On @MikeSpreitzer 's prompt, here's a list of issues for whom the observed behavior was similar to the one described in this issue: https://github.com/coreos/etcd-operator/issues/1330 https://github.com/coreos/etcd-operator/issues/1300 https://github.com/coreos/etcd-operator/issues/1962 https://github.com/etcd-io/etcd/issues/8803 https://github.com/etcd-io/etcd/issues/8268 https://github.com/kubernetes/kops/issues/6024
@myazid not that I know of. Are you experiencing it? If so, could you post more details?
I'm running into the same issue. Is anyone planning to fix this? Also, is it safe to pass a bogus value for path.home?
I'm also experiencing this.
Any update on this?
Hi @sravisun . I'm using a two-socket system where each socket is a [Xeon Silver 4114 CPU](https://www.intel.com/content/www/us/en/products/sku/123550/intel-xeon-silver-4114-processor-13-75m-cache-2-20-ghz/specifications.html). The OS is Ubuntu 22.04. pcm is at [release 202201](https://github.com/intel/pcm/releases/tag/202201). I have a...
Hi @sravisun. To disable hyperthreading, I update the grubconfig by appending `nosmt` to the value of the var `GRUB_CMDLINE_LINUX_DEFAULT`, run `update-grub`, and then reboot the machine. Besides the no-HT use...