Age | Commit message (Collapse) | Author | Files | Lines |
|
Etcd pod fails to start with file not found error.
The error is being caused because the pod is stuck
in an infinite loop as the readiness probe is not true.
Since, we are anyway checking the pod status, we removed
the readiness probe as it is not needed.
Bumped up version of etcd to 3.2.24
This fixes a known issue:
https://github.com/etcd-io/etcd/pull/4861
Issue-ID: MULTICLOUD-660
Change-Id: I815766b4a8f187d88bb2fcdb71e9d6e24b277d25
Signed-off-by: Kiran Kamineni <kiran.k.kamineni@intel.com>
|
|
The chart uses servicename in statefulset.yaml.
This should be fullname instead.
Issue-ID: MULTICLOUD-636
Change-Id: I0e523a5c0e2e2c432f3a159fcb8c9ddcd2240e68
Signed-off-by: Kiran Kamineni <kiran.k.kamineni@intel.com>
|
|
Based on the helm chart in github helm repo
https://github.com/helm/charts/tree/master/incubator/etcd
etcd required as datastore by k8s Plugin in
multi-cloud project.
Change-Id: Ie6c7d9fc394f2a08cd9d34dda6261da13ef005f3
Signed-off-by: Ritu Sood <ritu.sood@intel.com>
Issue-ID: OOM-1828
|